get_training_load_balance

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

No annotations are provided, so the description carries the full burden. It discloses the return semantics well: band loads, target ranges, feedback phrases, and the computation of 'below', 'within', or 'above' status. As a 'Get' tool it implies read-only behavior, and the description sufficiently characterizes what the caller will receive.

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?

Every sentence adds value: the definition, the intended use, the status semantics, and the parameter format. The description is front-loaded with the core purpose and contains no filler or redundancy.

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 single-parameter read tool with an output schema present, the description is complete. It explains what the tool does, when to use it, what the response contains conceptually, and how the date argument is formatted. No critical operational aspect is left unexplained.

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%, so the description must compensate. It adds the YYYY-MM-DD format for the date parameter and clarifies that the date anchors the trailing-month training load distribution. This is meaningful added context beyond the bare 'Date' property in the schema.

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: getting Garmin's Load Focus, with the exact scope of trailing-month load across three intensity bands. It also distinguishes itself from related siblings like get_training_load_trend by focusing on balance/distribution rather than trend.

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 explicitly says to use this tool to assess whether the training mix is balanced or deficient in a particular intensity band. It does not name alternative tools or give when-not-to-use conditions, but the use case is clearly stated.

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