get_vbat_scale

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

The description correctly indicates this is a read-only operation retrieving a UINT8 value with a default of 110. No annotations exist to contradict, but the description adds minimal behavioral detail beyond the tool name and type info.

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: a single sentence plus type information. It conveys the essential purpose and usage without any extraneous text.

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 getter with no parameters and no output schema, the description covers the core function, calibration context, and type/default info. It lacks details about the exact return format or integration with other calibration steps, but remains sufficient for the tool's simplicity.

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 tool has zero parameters, and the schema coverage is complete. The description does not need to explain parameters; the baseline score of 4 applies as it adds no confusion.

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 identifies the tool as retrieving the vbat_scale voltage divider calibration value. It explicitly states the purpose is for calibration ('Adjust until reported voltage matches a multimeter'), and the name and context distinguish it from set_vbat_scale and other battery-related get tools.

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 clear context that this tool is used in a calibration workflow, encouraging iterative check-and-adjust. However, it does not explicitly exclude alternative tools like get_vbat_divider or get_vbat_multiplier, though the calibration context differentiates it sufficiently.

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