get_nightly_recharge

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

No annotations provided, so description carries full burden. It discloses available data fields and a 28-day history limit, but omits details like error states (e.g., no data for a date), rate limits, or whether the tool mutates state. Adequate but not comprehensive.

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 sentences with zero wasted words. Front-loaded with the main verb and resource, then details. Exceptionally concise and efficient.

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 no output schema, the description adequately explains what data is returned. Mentions 28-day data availability but lacks details on what happens if date is out of range or how multiple dates are handled. Still fairly complete for a single-date retrieval tool.

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 coverage is 100%, but description adds significant meaning: explains the optional date parameter and that omitting it returns available data. Also lists the returned metrics (ANS charge, HRV, breathing rate, overall recovery), which the schema does not detail.

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?

Clearly states it retrieves Nightly Recharge data measuring overnight recovery. Lists specific included metrics (ANS charge, HRV, breathing rate, overall recovery) and distinguishes from sibling 'get_nightly_recharge_range' by implying a single date query.

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 explicit guidance on when to use this tool versus siblings like get_nightly_recharge_range or other health tools. The use case is implied from the name and description, but no when-to-use or when-not-to-use information is provided.

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