get_training_load_trend

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

With no annotations, the description carries the burden of disclosing behavior. It clearly explains that the tool returns per-day CTL, ATL, TSB, and ACWR values, defines the formulas, and states the 90-day maximum. This gives the agent useful behavioral context beyond the bare tool name, though it does not cover edge cases like inclusive date handling.

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-organized and front-loaded: purpose, return values, use case, range guidance, then parameters. Every sentence adds value, and there is no redundant or filler content.

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 read-only trend tool with an output schema, the description covers the essential semantics: what metrics are returned, how they are calculated, when to use it, and how far back it can go. It could be more explicit about date inclusivity and ordering, but the output schema and simple two-parameter interface keep this from being a significant gap.

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 does by documenting both parameters with their date format ('YYYY-MM-DD') and the overall date-range concept. The parameter names are self-explanatory, and the format hint adds critical information the schema does not provide.

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 states a specific verb and resource: 'Get the Performance Management Chart (CTL/ATL/TSB) over a date range.' It also names the exact metrics returned, distinguishing it from sibling trend tools like get_hrv_trend or get_vo2max_trend without needing to inspect their schemas.

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 gives clear use context: 'Use this to assess whether the athlete is building fitness, peaking, or accumulating too much fatigue.' It also provides recommended and maximum date ranges. It does not explicitly exclude alternatives or name sibling tools for comparison, so it falls short of full guidance.

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