set_current_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. It only states the action and options, but does not disclose behavioral traits like whether a reboot is needed, if the change is persistent, or any immediate effects on readings.

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 concise (two sentences) and front-loaded with the key action. It could be better structured (e.g., bullet points), but it covers the essential information 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?

For a simple one-parameter setter, the description covers the purpose and values. However, it lacks usage guidelines and behavioral transparency, making it minimally viable but with clear gaps.

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 input schema for the 'value' parameter is minimally described ('Value for current_meter (UINT8)'). The description adds significant meaning by explaining that 'ADC' means onboard shunt and 'ESC' means ESC telemetry current, and provides the default value. This enriches the parameter semantics beyond the 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 it sets the current_meter (current sensor source) and lists two options (ADC, ESC). The verb 'set' and resource 'current_meter' are specific. However, it does not explicitly distinguish from siblings like set_adc_device or set_battery_meter, but the purpose is clear.

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 explains what ADC and ESC mean and provides a default, giving some context. However, it does not explicitly state when to use this tool vs alternatives such as set_battery_meter, or provide prerequisites or side effects.

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