Garmin Onboarding (shared wellness profile)

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, and the description reinforces 'Read-only' while adding context about return contents (11 questions, profile state, missing fields) and shared profile reuse across connectors, going beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is four sentences, front-loaded with the core purpose, then workflow, then sharing context. Efficient with no wasted words, though slightly redundant with 'Read-only' earlier and later implied.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, workflow, and cross-connector reuse, but lacks details on the meaning of 'missing critical fields' and how response_format affects output. Given no output schema, slightly more detail would improve completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% per context, but both parameters have semantic descriptions in the schema. The tool description does not add any extra meaning for parameters beyond what the schema provides, so it meets the baseline but does not exceed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns the 11-question Delx wellness onboarding flow plus shared profile state and missing fields, distinguishing it from sibling tools like garmin_profile_get and garmin_quickstart by specifying shared-profile reuse across connectors.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs the agent to ask questions one-by-one and then call garmin_profile_update with explicit_user_intent=true, and mentions alternative {connector}_onboarding tools, providing clear when-to-use and workflow guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.