vrm_get_lithium_bms

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

No annotations are provided, so the description must disclose behavioral traits. It does not explicitly state that the tool is read-only or safe, nor does it mention authentication requirements. While the name implies a get operation, the description fails to add transparency beyond that.

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 that efficiently conveys the tool's purpose without any wasted words. It is appropriately front-loaded and every word 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?

Given the absence of an output schema, the description should provide more detail about the return data. It only says 'advanced cell monitoring and safety information', which is vague. The tool has moderate complexity with two parameters, but the description lacks completeness for an agent to fully understand what data to expect.

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 description coverage is 100% for both parameters ('siteId' and 'instance'), so the schema already provides clear descriptions. The tool description does not add any additional meaning or context to the parameters, thus it meets the baseline without exceeding.

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 Lithium battery BMS data', which is a specific verb and resource. Among siblings like vrm_get_battery_summary and vrm_get_bms_diagnostics, it distinguishes itself by mentioning 'advanced cell monitoring and safety information', indicating a more specialized focus.

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 such as vrm_get_battery_summary or vrm_get_bms_diagnostics. It lacks explicit when/when-not conditions and does not mention any alternative tools.

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