get_sleep

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

No annotations provided, so description carries full burden. Discloses deduplication logic, source field, precedence rule, and ordering. Implies read-only nature but does not explicitly state it.

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?

Single paragraph with logical flow: main purpose, deduplication details, usage guidance. Front-loaded and efficient, though slightly lengthy.

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 parameters (2, no required, no enums) and presence of output schema, description adequately explains tool purpose, parameters, and behavior relative to siblings. Could mention which fields are in output but output schema covers that.

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 coverage is 0%, but description adds significant meaning: `days` explained as 'last `days` days' with default, and `dedupe` explained in detail including default behavior and same-night precedence.

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?

Clearly states returns sleep session records from last `days` days, newest first, from two sources. Distinguishes from sibling `health_context` by saying 'Use this for sleep detail beyond what health_context() summarizes'.

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 says when to use (for sleep detail beyond summary) and explains dedupe behavior with same-night precedence. Implicitly suggests not to use when only summary is needed, but lacks explicit when-not-to-use.

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