garmin_get_training_status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds modest context about the single-date scope, but does not disclose behaviors like caching, refresh semantics, or data availability expectations.

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?

A single sentence, front-loaded with the action and resource, with no wasted words. Every word adds value and the structure is immediately scannable.

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 tool is simple (2 params, annotations provide safety, output schema exists), and the description covers the core purpose. However, it leaves gaps around the 'refresh' parameter and what exactly 'training status and readiness' entails, which could matter for an agent selecting this 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?

The description provides the date format 'YYYY-MM-DD' for the required 'day' parameter, adding meaning beyond the bare schema type. However, the optional 'refresh' parameter is not mentioned at all, and schema description coverage is 0%, so the description only partially compensates.

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 verb 'Get' and the specific resource 'Garmin training status and readiness' for a single date. This distinguishes it from sibling tools like garmin_get_day or garmin_get_sleep, making its purpose 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?

The description implies usage for a specific date ('for one YYYY-MM-DD date'), but does not explicitly state when to choose this tool over alternatives or provide exclusions. Sibling tools exist for other metrics, but no direct comparison is given.

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