get_sleep_data

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

No annotations are present, so the description carries the behavioral disclosure burden. It warns that the tool returns ~50KB of detailed data, which is meaningful context that helps an agent avoid unnecessarily large payloads. For a read-only getter with an output schema, this is solid behavioral transparency.

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 compact and front-loaded: the core purpose appears first, followed by a useful size warning and alternative, then the parameter format. Every sentence earns its place with no redundancy.

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 the tool's low complexity, an output schema, a single required parameter, and the description's format specification plus routing guidance, nothing essential is missing for an agent to correctly 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 only provides the property name 'Date', while the description adds the required YYYY-MM-DD format. With 0% schema description coverage, this compensation is essential and sufficient for the single parameter.

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 and resource ('Get full sleep data with all details') and explicitly contrasts with get_sleep_summary() by calling it the 'compact summary' option. This makes the tool's scope clear and distinguishes it from a sibling with overlapping intent.

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?

The note 'For a compact summary, use get_sleep_summary()' directly tells the agent when to choose the alternative. It also implies this tool is for cases where full, detailed sleep data is needed, so the routing guidance is explicit.

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