get_body_battery

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

No annotations are present, so the description must disclose behavioral traits. It only mentions input format and does not describe any side effects, rate limits, authentication needs, or data freshness. As a data retrieval tool, it likely has no destructive effects, but this is not stated.

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 concise with two clear sentences. The function is stated upfront, and parameter details follow. It could be slightly more informative without sacrificing conciseness, but it is well-structured.

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 and 15 sibling tools, the description lacks completeness. It does not describe the returned data structure or how to interpret Body Battery values. A user cannot infer what the output will look like or how to use it effectively.

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 0%, but the description adds meaning to both parameters: start is a required date in YYYY-MM-DD format, end is optional. This clarifies format and optionality beyond the schema's type info. However, it does not explain the meaning of the date range (e.g., inclusive vs exclusive) or expected data granularity.

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 retrieves Body Battery data for a period. The verb 'Get' and resource 'Body Battery data' are specific. It distinguishes from sibling tools like get_activities or get_sleep_data by focusing on body battery. However, it does not elaborate on what 'Body Battery' entails, leaving some ambiguity.

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 such as get_all_day_stress or get_stress_data. There are no mentions of prerequisites, use cases, or contexts where this tool is preferred.

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