body_battery

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the default date range and the returned metric categories, but does not state that the operation is read-only, how null dates are handled, or any data availability constraints.

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 two compact clauses with zero waste, and the default range is front-loaded as the key operational detail. Every phrase contributes useful information.

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?

With no output schema and no annotations, the description must carry all context. It covers the metric content and default range adequately, but omits date formats, handling of null parameters, and differentiation from similar summary tools, leaving real gaps.

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 description coverage is 0%, so the description must compensate. It only notes the default range and does not explain the expected date format, that both parameters are optional, or how start_date and end_date interact, leaving agents to infer parameter behavior.

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 names a specific resource (Body Battery) and the metrics returned: charging, consumption, highest/lowest value. It is clear what the tool retrieves, though it does not explicitly differentiate itself from sibling summary tools such as daily_summaries.

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 default of the last 7 days implies usage for recent Body Battery data, but there is no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no stated exclusions. Usage is implied rather than directed.

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