get_respiratory_events

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

Without annotations, the description carries the burden for behavior. It adds that large leak spans are reported separately, which is useful, but it does not disclose side effects, read-only nature, or the impact of the include_events parameter. The description provides some transparency but leaves key behavior unspecified.

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 sentences with no filler. It front-loads the core purpose and adds a brief behavioral note. Every word earns its place.

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?

The tool has 3 parameters, no annotations, and no output schema. The description covers the output shape in part but leaves parameter semantics and usage context unaddressed. For a tool with multiple parameters and no schema documentation, the description is not complete enough.

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 0% coverage and the description does not explain any parameters. 'one night' hints at the date parameter, but there is no mention of profile or include_events. The agent cannot infer what include_events toggles or what profile means.

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 tool provides individual respiratory events (apneas, hypopneas, RERAs) for one night, along with counts by type and an hourly histogram. This specific scope distinguishes it from siblings like get_daily_summaries or get_daily_detail.

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?

No guidance is given on when to use this tool versus alternatives. The note about large leak spans being reported separately is a behavior nuance, not a usage context. The tool does not mention exclusions or alternatives.

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