Connect generated metadata with the app’s service entry point.
1. Build setup
Use the current AppFunctions dependencies, compile SDK and KSP configuration from the supported setup. Alpha releases can change registration patterns; do not combine incompatible examples.
2. Service entry point
Keep the function service connected to your domain layer rather than embedding business logic in generated plumbing. Verify that the configured entry point is discoverable.
3. Metadata generation
Names, parameter descriptions and result types help callers understand the function. Build-time generation must be inspected and verified on-device; compilation alone does not prove registration.
Worked scenario
A function compiles but its service configuration is missing. Discovery finds nothing, so the first debugging target is registration rather than model prompting.
Apply it
Expose one read-only function and inspect its registered identifier and metadata using the supported tools.
Check your understanding
The function appears in device-level discovery with the intended schema. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.