get_training_load_balance

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

With no annotations, the description carries the full behavioral burden. It discloses meaningful logic: each band reports load alongside a target range, and a status of below/within/above is computed relative to that range. It also explains the feedback phrase with examples. It does not explicitly state read-only behavior, but the 'get' verb and absence of mutation language make it reasonably inferable.

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 well-structured and front-loaded: a one-sentence definition, a one-sentence use case, a compact explanation of the output status, and a single parameter listing. Every sentence contributes necessary information without fluff or repetition.

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 getter with an output schema available, the description is complete enough. It covers what the tool returns, how status is derived, what the feedback phrase means, and the expected date format. The output schema presumably handles the full return structure, so the description does not need to re-document it.

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 provides the date format ('YYYY-MM-DD') and gives context by describing the trailing-month load distribution, implying that the date anchors the trailing month. This adds meaning beyond the bare schema field, though it could further clarify valid date ranges or what happens if no data exists.

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 opens with a specific verb and resource: 'Get Garmin's Load Focus,' and immediately defines the exact content: the distribution of training load across three intensity bands plus a feedback phrase. It is clearly distinct from siblings like get_training_load_trend because it names the specific metric and its components.

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 includes an explicit use statement: 'Use this to assess whether the athlete's training mix is balanced or deficient in a particular intensity band.' It gives clear context for when to invoke the tool, though it does not mention alternatives or when not to use it, which prevents a 5.

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