Garmin Profile Get (shared wellness profile)

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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds context about the shared profile location and cross-connector nature, but does not disclose what happens if the profile is missing or other edge cases. Since annotations cover the safety profile, the description adds sufficient value.

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 three sentences, concise and well-structured. The first sentence states the action, the second lists returned data, and the third provides cross-connector context. It is efficient with no wasted words.

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?

Given no output schema, the description covers the types of returned data (preferred name, goals, etc.) but does not specify exact fields or structure. It lacks information on error conditions or missing profile. The presence of a similarly named sibling adds ambiguity. Overall, adequate but with gaps.

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?

The schema has 0% description coverage, yet the description does not explain the single parameter 'response_format' (enum: markdown/json, default: markdown). The parameter controls output format, which is important for an AI agent to know. The description misses this opportunity to add meaning beyond the schema.

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 it reads a shared wellness profile and lists the types of data returned. It mentions cross-connector availability, which aids in distinguishing from other MCP tools, but does not explicitly differentiate from the similarly named sibling 'garmin_get_profile'.

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?

The description does not provide guidance on when to use this tool versus alternatives like 'garmin_get_profile' or other profile-related tools. It only implies usage for reading the shared profile, with no explicit when-to-use or when-not-to-use statements.

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