get_health_summary

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

With no annotations, the description carries the full burden of behavioral disclosure, but it provides minimal detail. It does not explain what 'compact' means, how the combination works, or what the output structure is, leaving the agent to guess about the tool's behavior.

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 a single, concise sentence with no wasted words. It is front-loaded and easy to parse. However, it omits important contextual details, so it is efficient but not fully comprehensive.

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?

Despite having an output schema, the description is incomplete. It does not provide usage guidelines or parameter semantics, and the tool has multiple similar siblings. More context is needed for an agent to confidently select and invoke this tool.

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 has one parameter 'days' with 0% description coverage. The tool description does not mention this parameter at all, so the agent gets no additional semantic context about how 'days' affects the result. The parameter name alone is insufficient.

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 that this tool provides a compact health snapshot combining recovery, sleep, and stress. It uses a specific verb ('get' implied) and resource ('health summary'), and the combined scope distinguishes it from sibling tools like get_recovery, get_sleep, and get_stress.

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 guidance is provided. The description implies a combination use case but does not explicitly mention alternatives or when not to use this tool. Given the large sibling set, this lack of guidance could confuse an agent.

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