get_battery_meter

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

Without annotations, the description must convey behavioral traits. It reveals the return type (UINT8), default (ADC), and possible values, which is adequate for a simple read-only tool. However, it does not explicitly state that no side effects occur or describe the exact output format.

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 very short and to the point. It includes necessary abbreviations and default value efficiently. Could be slightly more structured, but overall it is concise without unnecessary words.

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 simplicity of the tool (no parameters, read-only) and no output schema, the description sufficiently indicates that it retrieves the battery voltage source and explains the options. It is complete enough for an agent to understand the tool's purpose and expected return.

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?

There are no parameters; the schema coverage is trivially 100%. The description adds no parameter information beyond the schema because none exist. Baseline of 3 is appropriate.

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 tool name and description clearly state it retrieves the battery voltage reading source. It explains the two possible sources (ADC and ESC), making it distinct from the many other get_* tools and the set_battery_meter sibling.

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?

No guidance is provided on when to use this tool versus alternatives. While a sibling set_battery_meter exists, there is no mention of when to use get vs set, or any other usage context.

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