garmin_load_focus

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

With no annotations, the description carries the full behavioral burden. It doesn't say whether the data is read-only (implied), what time window is used, whether results are cached or rate-limited, or what the focus_status values mean. It states what is reported but nothing about behavior or constraints.

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 short and front-loaded, leading with the primary measure. It is slightly redundant in restating the zone breakdown in a second sentence, but it remains 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?

Since an output schema exists, the description needn't explain return values, and it correctly avoids that. However, for a no-annotation tool, it leaves the time window, data source, and interpretation of focus_status unaddressed, which is a gap for an analytics 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?

There is a single 'days' parameter (default 28) with 0% schema description coverage, so the description could have clarified it but does not. With one parameter and zero coverage, the description adds no meaning beyond the schema; baseline 3 is appropriate.

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?

Names the specific measure (training load distribution) and enumerates the zones it reports, so the purpose is clear. It does not, however, differentiate itself from the closely related sibling garmin_training_load, which an agent could easily confuse it with.

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?

There is no statement of when to use this tool versus alternatives such as garmin_training_load or garmin_training_status. The reader must infer the use case purely from the noun phrase describing the output.

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