withings_get_sleep

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

With no annotations present, the description carries the behavioral disclosure burden. It adds useful context beyond the raw operation: the default 24-hour time window, the high-frequency/nightly-scope behavior, and typical source devices. It does not mention limits or output volume, but the notable traits are disclosed.

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?

Three short sentences, each earning its place: the core behavior, the default range, the sibling differentiation, and context about typical sources. Key information is front-loaded with no filler or redundant restatement of the tool name.

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 simple tool with three optional, fully documented parameters, the description plus schema covers the essential invocation details. The only minor gap is a lack of explicit return-structure or data-format details, but the described series fields give a reasonable expectation.

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 description coverage is 100%, so the schema already fully documents startdate, enddate, and data_fields including defaults. The description reinforces the 24-hour default and mentions series fields, but adds no parameter semantics beyond what the schema provides, so baseline 3 is appropriate.

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 states a specific verb ('Fetch'), a precise resource ('high-frequency sleep stage and vital series'), and the data categories ('stages, HR, respiration, snoring, HRV'). It clearly differentiates itself from withings_get_sleep_summary, so an agent can distinguish it from its closest sibling without opening the schema.

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 gives explicit routing guidance: 'Prefer withings_get_sleep_summary for multi-night overviews; use this for detailed series within a night.' This tells the agent both when to use this tool and when to avoid it in favor of a named alternative.

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