Garmin Body Battery

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds only 'Not medical advice', which is a disclaimer but not a behavioral trait. With rich annotations, the description provides minimal additional transparency, scoring at baseline.

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 extremely concise at two sentences, with no wasted words. It immediately conveys the core action and includes a necessary disclaimer. The structure is front-loaded and efficient.

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?

Given the tool's simplicity, presence of an output schema, and detailed annotations, the description is adequate but lacks some helpful context (e.g., what the body battery report contains, typical values, or when to use privacy_mode). It does not contradict annotations, but could be more informative about the return data.

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?

Parameter descriptions are already provided in the schema for 2 of 3 parameters (67% coverage). The description does not add any extra meaning beyond what the schema offers, such as explaining what 'Body Battery' is or how the report is structured. Baseline score is appropriate.

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 states the action ('Get'), the resource ('Garmin Body Battery daily report'), and the primary parameter ('for a date'). It distinguishes itself from sibling tools like garmin_get_body_battery_events by specifying 'daily report', making its purpose unambiguous.

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 no guidance on when to use this tool versus alternatives (e.g., garmin_get_body_battery_events) and does not mention any prerequisites or context for use. The only contextual clue is the date parameter, but no explicit usage criteria.

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