get_body_battery

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

With no annotations, the description carries the behavioral burden. It discloses a useful non-obvious limit: the optional series is capped at 48 points. As a read-oriented 'get' tool, the behavior is largely clear, though edge cases like date handling or unavailable data are not mentioned.

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 a single sentence with no filler. It front-loads the core purpose and then adds only the important series limitation. Every word contributes.

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?

For a simple two-parameter read tool with an output schema, the description covers the essential selection and invocation details. It explains the tool's purpose and the key series cap, though it could have briefly addressed the date parameter's expected format.

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 loosely maps 'daily' to the date parameter and 'optional series' to include_timeseries, and adds the 48-point series cap. However, it does not specify date formats, the meaning of the series points, or better describe the boolean's 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 clearly identifies the resource ('Garmin Body Battery'), the verb ('Get'), and the daily scope. It also distinguishes an optional series mode, which helps separate this tool from sibling metrics like get_hrv or get_sleep.

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 provides clear usage context: it returns a daily Body Battery value, with an optional series. It does not mention when not to use it or point to alternatives, so it stops short of full usage guidance.

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