get_sleep_summary

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully states the conditional return behavior ('sleep-related fields if available, otherwise the full dict'), but it does not clarify what happens when 'day' is null, what 'full dict' entails, or any other side-effect/authorization context.

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 two concise sentences, front-loads the core purpose, and adds a valuable behavioral detail without 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?

For a single-parameter read tool with no output schema, the description covers the basic mechanics but leaves ambiguity around a null 'day' value and the exact composition of the 'full dict'. An agent could still call it, but may not fully understand the response without additional inference.

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 no parameter descriptions (0% coverage), so the description must compensate. It provides the date format YYYY-MM-DD for the 'day' parameter, which is helpful. However, it omits the meaning of the default null value and does not explain how the parameter controls the summary.

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 resource (daily summary) and the behavior (returns sleep-related fields or falls back to the full dict), which distinguishes it from siblings like get_sleep_detail. It does not explicitly name alternatives, so it misses the top score.

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?

There is no guidance about when to use this tool versus alternatives such as get_sleep, get_sleep_detail, or get_daily_summary. The only clue is the phrase 'sleep summary', but no explicit when-to-use or when-not-to-use instructions.

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