get_training_readiness

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states that the tool gets readiness data; it does not reveal whether the date is required, what happens when no date is given, whether it returns data for multiple days, or any side effects. 'Get' implies read-only, but the description does not explicitly confirm this.

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, efficient sentence that names the resource and key output components with no fluff. It loses a point because the extreme brevity omits necessary context about the date parameter, but the existing text is well-structured and front-loaded.

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?

For a tool with one optional parameter and an output schema, the description provides a minimal but acceptable overview of the return value. However, it is incomplete for correct invocation: it does not explain the role of the date parameter or how this tool fits among the many similarly named readiness/recovery siblings.

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 for the only parameter, 'date'. The description does not mention the date parameter at all, so the agent must infer formatting, meaning, and default behavior from the schema's title and default value alone. The description fails to compensate for the low schema coverage.

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 a specific verb and resource ('Get Garmin training readiness') and adds detail about the expected response contents ('component percentages, and factor feedback'). This distinguishes it from generic sibling tools like get_sleep or get_activities, though it does not explicitly contrast with get_recovery or get_body_battery.

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 guidance is provided about when to use this tool instead of siblings like get_recovery, get_body_battery, or get_daily_summary. The description does not mention whether it supports a specific date, how it relates to other readiness metrics, or what inputs should be supplied.

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