set_battery_meter

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

No annotations are provided, so the description carries the full burden of disclosure. While it mentions the default value and possible options, it does not disclose other behavioral traits such as whether the setting persists after reboot, if any validation occurs, or if there are side effects (e.g., impacting other measurements). The information is minimal for a mutation tool.

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 (three short sentences plus a type/default note). It front-loads the purpose, then explains the two possible values, and ends with technical details. Every sentence adds value without 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 single-parameter set tool, the description covers the purpose, allowed values, and default. It does not explain return values or confirmation, which is acceptable given no output schema. It could mention if setting requires reboot, but overall it sufficiently equips an agent to use the tool.

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 describes the parameter as 'Value for battery_meter (UINT8)', which is generic. The description adds meaningful semantics by specifying the two allowed values ('ADC' and 'ESC') and the default. This goes beyond the schema and helps the agent understand valid inputs.

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 states the tool's purpose with a specific verb ('Set') and resource ('battery_meter'), clearly indicating it is for setting the source of battery voltage reading. It distinguishes itself from siblings like set_current_meter by focusing on battery_meter and mentioning the two possible values (ADC and ESC).

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 does not provide any guidance on when to use this tool versus alternatives (e.g., when to choose ADC vs ESC). It also does not mention when not to use it or any prerequisites. The sibling list contains many set_* tools, but no direct alternative context is given.

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