Garmin Agent Manifest

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

Annotations already indicate readOnlyHint, destructiveHint, idempotentHint. The description adds value by disclosing that the tool does not call external services or expose secrets, providing behavioral context beyond the annotations. This is useful for the agent's safety reasoning.

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 a single sentence with an additional clarifying sentence. It is front-loaded with the core purpose and uses no filler. Every word earns its place, making it highly efficient.

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 the tool is simple (2 optional params, output schema exists), the description provides minimal context about the manifest content. It does not specify what information the manifest contains or how the agent should use it. The output schema may cover structure, but the description lacks high-level guidance, making it only marginally complete.

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 description coverage is 0%, yet the description does not explain the 'client' and 'response_format' parameters. While the parameter names and enums are somewhat self-explanatory, the description should add meaning—e.g., what each client value implies or how response_format affects output. Without this, the agent lacks guidance on parameter usage.

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 provides 'install, runtime and client guidance for AI agents' and explicitly notes it 'Does not call Garmin or expose secrets.' This distinguishes it from data-retrieval sibling tools, making its purpose highly specific and unambiguous.

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?

No explicit guidance on when to use this tool vs alternatives. The description does not mention prerequisites, ordering relative to other tools, or scenarios where this tool is appropriate. The agent must infer from the tool's purpose alone.

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