daily_summary

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

No annotations are provided, so the description carries full responsibility. It discloses that the tool combines the latest recovery score, last night's sleep, and today's accumulated strain, and mentions that last_sleep includes local bedtime and wake time. However, it does not specify data freshness, caching behavior, or whether values are real-time or from the last sync. This is adequate but not exhaustive.

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 brief but complete: two sentences cover purpose, contents, and usage context. Front-loaded with the core benefit, then details. No wasted words.

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?

Given zero parameters and no output schema, the description provides a good overview of what is returned (recovery, sleep, strain). It could describe the output format or data types, but the description is suitable for the tool's simplicity. Omitting details like range or units is a minor gap.

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 tool has zero parameters, so the description adds value by explaining what the snapshot includes (recovery, sleep, strain) and that it reflects the current state. Schema coverage is 100%, so a baseline of 3 is adjusted upward for the added context above the empty schema.

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 'snapshot of how the user is doing RIGHT NOW' combining recovery, sleep, and strain. It distinguishes itself from sibling tools by being a composite view, unlike individual metric tools like get_recovery or get_sleep.

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 tells the agent to use this first when the user asks about current state, listing specific queries like 'how am I doing', 'am I recovered', 'did I sleep well'. Implicitly guides away from using separate sibling tools until a more detailed view is needed.

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