stress

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

No annotations exist, so the description carries the full burden. It usefully discloses the default time window, which is real behavioral context, but says nothing about read-only nature, data source, timezone, or what the averages represent.

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 short sentences, front-loaded with the metric and then the default. Nothing is wasted, though the structure could be slightly clearer about the date parameters.

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?

A read-only aggregation tool with two entirely undocumented date parameters and no output schema. The description should at minimum state accepted date formats and whether the result is a per-day series or a single average.

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% and the description does not explain the start_date/end_date parameters at all — no date format, no inclusivity. The default-window sentence gives only indirect context for the parameters.

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?

States the resource and metric precisely ('Durchschnittlicher Stress pro Tag'), which clearly separates it from siblings like hrv_summaries or sleep_summaries. It lacks an explicit verb, but the aggregation intent is unambiguous.

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 default window ('letzte 28 Tage') gives useful context for calling with no arguments, but there is no guidance on when to use this versus related summary tools or on any exclusions. Usage is only implied.

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