Get body battery

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

Annotations already declare readOnly and open-world access. The description adds meaningful behavior: default 7-day range, 31-day-at-a-time fetching for long ranges, and that omitting chunks leaves out fine-grained readings to keep responses small.

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?

Front-loads what the tool returns, then explains each parameter compactly. The date and chunks details are concise, with no filler or repetition.

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?

No output schema exists, but the description explains the included data and the response-size tradeoff from chunks, which is enough to invoke the tool correctly. Exact response fields and structures remain unspecified but are not essential to call semantics.

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 carries the full parameter burden and does so well: it documents start/end format, inclusivity, default range, arbitrary range length with 31-day fetching, and chunks as intervals with lowest/highest levels and omitted raw readings.

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?

States a specific verb and resource: daily Body Battery data with amount charged/drained and events that moved it. The Body Battery resource distinguishes it from siblings like get_stress or get_daily_summary, though it does not explicitly contrast them.

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?

Implies usage for retrieving Body Battery history and gives a useful default range plus a chunks use case. It never says when to choose this over related tools such as get_stress, get_day, or get_daily_summary.

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