get_body_battery

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

No annotations are provided, so the description carries the behavioral disclosure burden. It discloses that the tool returns body battery levels across the day, but it does not mention granularity, units, timezone handling, or any error/edge-case behavior. It is adequate but not rich.

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?

Two short sentences with no filler. The action, resource, date format, and return meaning are all front-loaded and each sentence earns its place.

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 one-required-parameter getter with an output schema, the description is nearly complete. It includes the date format and a meaningful description of the returned data, though it lacks explicit caveats about what exactly the returned levels represent beyond 'throughout the day.'

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 only defines `date` as a string with title 'Date' and 0% schema description coverage. The description compensates by specifying the required format 'YYYY-MM-DD', which is essential for correct invocation.

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 specific verb ('Get') and resource ('body battery data') and adds a helpful semantic definition ('energy reserves throughout the day'). It is easily distinguished from sibling health-metric tools because it names a unique resource and a single-date scope.

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 gives clear context for when to use it: retrieve body battery data for a specific date. It does not explicitly mention alternatives or exclusions, but among the siblings only one tool targets body battery, so the intended usage is clear.

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