get_body_battery_events

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

No annotations are provided, so the description carries full burden. It mentions the event types but does not disclose read-only nature, auth requirements, rate limits, or whether events are chronological. For a read tool, basic transparency is present but limited.

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, no wasted words. It could be slightly more structured (e.g., listing event types in a bullet), but it is acceptably concise.

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 single-parameter read tool, the description gives a clear purpose and example events. However, it does not mention the return format (e.g., list of events with timestamps, types) since no output schema exists. The description could be more complete regarding what data is returned.

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 coverage is 100% (single 'date' parameter with format and description). The description adds context that the date is for events affecting energy levels, but this is partially redundant with the schema's 'date' description. It adds marginal value beyond schema.

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 'Get Body Battery events for a date' and specifies event types (sleep, activities, naps). It distinguishes from sibling tools like 'get_body_battery' (which likely returns overall battery levels) and 'get_sleep_data' (sleep-specific). The verb 'Get' and resource 'Body Battery events' are precise.

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 usage for viewing events that affected energy levels, but does not explicitly state when to use this tool vs alternatives like 'get_body_battery' or 'get_sleep_data'. No when-not-to-use or alternative tool references are provided.

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