Get Body Battery

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

The readOnly and openWorld annotations already cover safety and side-effect expectations. The description adds context about charged/drained periods and sleep impact, which is useful, but there is no mention of potential limitations, errors, or data granularity.

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 and well-structured, consisting of three focused sentences with no redundant information or fluff.

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 lack of an output schema, the description gives a high-level glimpse of the returned data (energy levels, charged/drained periods, sleep impact) but does not specify the format, structure, or granularity of the response. This is adequate but not highly detailed.

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 already fully describes startDate and endDate (format, defaults). The description's mention of 'date range' adds no additional semantic meaning beyond what the schema already provides.

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 action (Get) and the resource (Body Battery energy level data). It also explains what Body Battery tracks and mentions date-range scoping, which distinguishes it from sibling tools like get_body_battery_events.

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 description implies usage for retrieving energy level data over a date range but does not explicitly differentiate it from similar tools like get_body_battery_events. No direct comparison or exclusion criteria is provided.

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