Health overview

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

Annotations already declare readOnlyHint=true. The description adds the specific window (7-180 days) and the content (trends, correlations, etc.), providing meaningful behavior context beyond annotations. No contradictions.

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?

Two sentences, no wasted words. Front-loaded with purpose, then details content. Every sentence earns its place.

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 tool with one optional parameter and existing output schema, the description provides sufficient context: window range, content types, and recommended usage. Complete for an agent to understand what the tool returns.

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?

Only one parameter 'days' with default 90, but schema description coverage is 0%. The description implies the parameter controls the window with '7-180 day window', but does not explicitly mention the parameter name, default, or that it's optional. Partially compensates for missing schema descriptions.

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 the tool provides a holistic overview of health metrics (status, trends, training load, personal records, correlations) over a 7-180 day window. It uses specific verbs and distinguishes itself from sibling tools by calling it the 'best first call' for a full picture.

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?

Explicitly says it's the best first call for 'give me the full picture of my health', indicating when to use. Does not explicitly list alternatives or when not to use, but the context of sibling tools like get_recovery_trends implies specificity. Slight improvement possible.

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