bosch_get_batteries

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

With no annotations provided, the description carries the burden of behavioral disclosure. It explains that each sync captures a snapshot and how latest_only affects results, which adds context. However, it does not explicitly state that this is a read-only operation or disclose any side effects, authorization requirements, or rate limits, leaving some ambiguity for an agent.

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 well-structured and appropriately sized. It opens with a clear one-liner, lists return fields, explains the snapshot/history behavior, and then details parameters. Every sentence adds value, and the use of bullet-like formatting improves readability.

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 absence of annotations and the presence of an output schema, the description is largely complete. It explains the tool's purpose, parameters, and the snapshot/time-series model. The only notable gap is the lack of comparison with overlapping sibling tools, which is more relevant to usage guidelines but also affects overall completeness in a broader toolset.

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 has no descriptions for parameters (0% coverage), but the tool description includes an Args section that thoroughly explains each of the 4 parameters: bike_id, start_date, end_date, and latest_only. It provides formats, defaults, and behavioral meaning (e.g., '30d' shorthand, 'return most recent snapshot'), fully compensating for the schema's lack of detail.

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 tool gets battery state and health for a Bosch eBike, listing the specific data fields returned. This is a specific verb+resource, but it does not explicitly differentiate from sibling tools like bosch_get_soc and bosch_get_capacity, which serve overlapping purposes.

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 offers usage guidance for parameters (e.g., 'Use latest_only=False with a date range to see history') but does not explain when to choose this tool over alternatives like bosch_battery_trends or bosch_get_soc. The context implies this is the comprehensive battery snapshot tool, but no explicit exclusions or alternatives are given.

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