Get Stress by Hour

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

The annotations declare readOnlyHint=true and openWorldHint=true, and the description respects that filtering model — it accurately describes a pure read of hourly summaries. While it doesn't discuss pagination or rate limits, it does specify the exact aggregated values returned, adding context beyond the annotations. For a read-only tool this is adequate.

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 with zero waste. The first sentence states the output exactly; the second adds usage guidance and routes to the alternative. The purpose is front-loaded and every clause 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 one-parameter, read-only aggregate tool with complete schema coverage and no output schema, the description captures everything an agent needs: what is returned, when to use it, and what to use instead. Nothing critical is missing.

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?

The schema already documents the single 'date' parameter with a format pattern and example, so schema description coverage is 100%. The description mentions the date implicitly ('a day') but adds no information beyond the schema's parameter documentation.

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 uses a specific verb ('get') and clear resource ('stress of a day'), and precisely enumerates the return content — average, maximum, stress band for each hour, plus day totals. This fully distinguishes it from get_stress_data and other siblings at a glance.

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?

It explicitly names the sibling tool (get_stress_data) and explains the decision rule: use this for hourly detail, use the sibling for the whole day, and use includeValues for three-minute samples. It also tells the agent when to use it — to see when stress rose or fell.

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