set_adc_vrefint_calibration

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention if changes take effect immediately, require a reboot, or are persistent. There is no indication of destructive potential or required permissions.

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 line that efficiently conveys purpose and parameter constraints. It is front-loaded and contains no unnecessary words, though it redundantly repeats the tool name.

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 setter with one parameter and no output schema, the description lacks context about the significance of the factory calibration, persistence, or the need for a reboot. The sibling tools include a getter, but the setter description does not complete the picture.

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 coverage is 100% with a clear property description. The description adds the default value 'default: 0', which is not in the schema, providing an extra hint. This is a small but valuable addition 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 the action 'Set' and the resource 'adc_vrefint_calibration' with additional context 'ADC internal voltage reference calibration (factory)', making it unambiguous and distinct from sibling set 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?

No guidance on when to use this tool versus alternatives. It mentions 'factory' but does not explain whether it is for initial setup only or for recalibration, nor does it specify 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.