Garmin Demo

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

Beyond annotations that mark it as read-only and idempotent, the description adds critical context: it returns example payloads and does not make real API calls. No contradictions with 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?

Single sentence capturing purpose and target tools. No wasted words; front-loaded with the key action.

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 serves as the contract by naming the three example tools. It could mention that payloads are realistic but not live data, but still adequate for a demo tool.

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?

With 0% schema description coverage, the parameter (response_format) is not explained in the description, but it is self-explanatory via its enum. The description does not 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 the tool returns 'realistic example payloads' for three specific tools, distinguishing it as a demo/preview tool among siblings that make actual Garmin Connect calls.

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 implies using this tool before making real calls to understand the data contract, but does not explicitly state when not to use it or mention alternatives. Clear enough for its demo purpose.

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