bosch_get_soc

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

With no annotations provided, the description carries the full burden. It discloses that the tool calls the Bosch mobile API live with no caching, which is useful. But it omits error behavior, what happens when the bike is inactive, and doesn't explicitly state that the operation is read-only.

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 appropriately concise, front-loading the purpose and then giving return values, prerequisites, a live-API note, and parameter guidance. Every sentence adds value with no redundancy.

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-parameter read tool with an output schema, the description covers purpose, returned data, prerequisites, data availability, and parameter provenance. It is slightly vague on what 'recently active' means and doesn't cover error scenarios, but overall it is complete enough for an agent to use the tool effectively.

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 0%, but the description provides essential parameter meaning: 'bike_id: The bike UUID from bosch_get_bikes.' This tells the agent exactly where to obtain the parameter value, fully compensating for the bare input 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 the verb and resource: 'Get live state-of-charge from the Bosch ConnectModule.' It also specifies the output values (battery percentage, charging status, remaining energy, range per assist mode), making it distinct from sibling battery-related tools like bosch_get_batteries or bosch_get_capacity.

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 on when the tool is usable: it requires a ConnectModule and only returns data when the bike is powered on, charging, or recently active. However, it does not explicitly mention alternatives or exclusions relative to sibling tools, so it slightly falls short of a 5.

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