query_sleep_data

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

Annotations readOnlyHint=true already indicate no destructive effects. The description adds detail on the specific sleep metrics retrieved but does not disclose any additional behavioral traits such as data freshness, rate limits, or authentication requirements. The description is consistent with annotations but adds only content detail.

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 concise, with two short paragraphs. It front-loads the main action and then lists retrieved data. Every sentence adds value, but the first line could be considered a title; overall it is well-structured.

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 presence of an output schema, the description adequately explains the tool's purpose and the data it retrieves. Parameters are fully described in schema. It does not cover error conditions or prerequisites, but for a simple read-only tool, it is sufficient.

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 input schema covers 100% of parameters with descriptions, so baseline is 3. The description confirms support for single date or date ranges, aligning with the schema, but adds no new meaning. The parameter descriptions in the schema are already clear.

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 uses the verb 'Get' with the resource 'sleep data and analysis'. It lists specific metrics, distinguishing it from sibling tools like query_health_summary which is broader. The purpose is unambiguous.

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 description mentions support for single date or date range queries, providing basic usage context. However, it does not explicitly state when to use this tool versus alternatives like query_health_summary, nor does it provide exclusion criteria. Usage guidance is implied but not explicit.

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