get_respiration_data

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently reveals that the tool returns detailed interval data and warns about the ~20KB payload size. It does not mention error behavior or date-timezone semantics, but for a read-only data retrieval tool this is solid disclosure.

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 the key usage note and argument documentation. Every sentence contributes value without fluff or unnecessary repetition.

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 single-parameter read-only tool with an output schema, this description is effectively complete. It describes what the tool returns, why this tool may be chosen over its summary sibling, and the required date format. No critical invocation detail is missing.

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 provides only a 'date' string with no description or format, so the description compensates by explicitly specifying YYYY-MM-DD format. This adds meaningful guidance beyond the schema, though it does not elaborate on the exact meaning of the date (e.g., timezone or end-of-day handling).

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 ('Get'), a clear resource ('full respiration time-series data'), and distinguishes itself from get_respiration_summary by emphasizing 'detailed interval data'. An agent can immediately tell this tool returns raw, granular respiration measurements rather than a compact summary.

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 explicitly states when to prefer get_respiration_summary: when a compact summary is desired. This gives the agent a clear decision rule and names the relevant alternative, making the usage context unambiguous.

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