respiration

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

No annotations exist, so the description carries full burden for behavioral disclosure. It only mentions 'current day respiratory data' with no details on permissions, data granularity, availability, or any side effects. This is severely insufficient.

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 extremely short (7 Chinese characters), which is concise but at the cost of essential information. It does not earn its place because it fails to provide the necessary context for effective tool selection and use.

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 has one parameter, no annotations, and many sibling tools, the description is woefully incomplete. It does not explain the date parameter, return structure (despite an output schema existing), or give any guidance on proper usage. The agent cannot reliably invoke this tool based solely on this description.

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 sole parameter 'date' has no schema description (0% coverage). The description implies that without a date, today's data is returned, but it does not explain the parameter's format, allowed values, or how to specify other dates. Partial compensation, but largely missing.

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 resource (respiration data) and temporal scope (current day). However, it lacks an explicit action verb (e.g., 'get', 'retrieve'), relying on the tool name to imply retrieval. This is moderately specific but could be more precise.

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 provided on when to use this tool versus alternatives. Among many sibling tools (e.g., resting_hr, spo2, stress), the description gives no context for selection, prerequisites, or exclusions.

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