get_body_battery

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

With no annotations, the description carries the burden of disclosing behavior. It clearly states what data is returned, but it does not explain behavior around optional inputs like date nullability or include_timeseries, nor does it mention any side effects or access requirements.

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, efficient sentence with no filler. It front-loads the tool's purpose and includes useful output details without becoming verbose.

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?

The output schema covers return values, but the description lacks guidance on parameter behavior and usage when to use this tool versus siblings. It is adequate for a simple read operation but leaves optional-input semantics and selection context to the agent.

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 input schema has 0% description coverage, so the description must compensate. It vaguely maps to the date parameter through 'for one day', but it says nothing about include_timeseries, date format, or what a null date means. An agent would need to infer most parameter semantics.

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 uses a specific verb ('Get'), names a clear resource ('Garmin Body Battery'), and specifies scope ('for one day'). It also enumerates the main outputs (charged/drained, start/end/high/low levels), which distinguishes it from sibling tools like get_sleep or get_daily_summary.

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 this is the tool for day-level Body Battery data, but it gives no explicit guidance on when to choose it over alternatives like get_daily_summary. There are no stated conditions, exclusions, or references to sibling tools.

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