Get Training Load And Recovery

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It indicates a read-only operation ('Get') and specifies the data source ('latest workout'), but does not detail behavior such as what happens if no workout exists, data freshness, or computation method. It also does not state whether this is a safe read operation, though 'Get' implies read-only.

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 that is concise and front-loads the core purpose ('Get current training load, recovery hours...'). It does not waste words and is easy to scan.

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 has zero parameters and an output schema (though not shown), the description could be sufficient. However, for a data retrieval tool with no annotations and no explicit behavior on edge cases (e.g., no workout found), it lacks critical context. The output schema may cover return values, but the description does not mention it or guide on interpretation. It is adequate but not thorough.

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 input schema is empty with 100% schema description coverage (trivially), so the description adds no parameter details. Since there are no parameters, baseline is 4, but the description clarifies the scope ('latest workout'), which provides some contextual meaning beyond the schema. However, it does not elaborate on any implicit defaults (e.g., timezone, units).

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 retrieves training load and recovery metrics (TSS, PTE, EPOC, recovery status) from the latest workout. This distinguishes it from siblings like get_training_summary or get_recent_workouts, though it does not explicitly name alternatives.

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 it is used for the latest workout's load and recovery data, but does not explicitly state when to use it versus get_training_summary or get_recent_workouts. It gives some context ('latest workout') but lacks clear exclusions or alternative guidance.

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