get_health_summary

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

No annotations are provided, so the description carries the full burden. It does disclose the content composition (recovery, sleep, stress) and implicitly what is excluded, which is useful, but says nothing about aggregation behavior, freshness, or how values are summarized. The presence of an output schema offloads return-shape disclosure, which keeps this at a 3.

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?

One short sentence, front-loaded with the core value proposition ('compact health snapshot') followed by the domains covered. No filler.

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 aggregate tool with a fully documented schema and an output schema, the description covers what the tool returns well enough. The one real gap is routing guidance against get_full_snapshot and the single-domain siblings.

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 100% ('Lookback window in days.'), so the single parameter is already fully documented in the schema. The description adds no meaning beyond that, so the baseline 3 applies.

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 a specific verb+resource (health snapshot) and its scope: it combines recovery, sleep, and stress. The word 'compact' implicitly distinguishes it from get_full_snapshot and from the single-domain siblings (get_recovery, get_sleep, get_stress), though it never names them.

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?

No when-to-use or when-not-to-use guidance is given. The agent is left to infer that a compact combined snapshot is preferable to get_full_snapshot or to three separate calls; nothing in the description says so.

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