get_adc_vrefint_calibration

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

The description indicates the tool retrieves a factory calibration value, implying a read-only operation. However, no annotations exist to confirm safety, and the description does not explicitly state behavioral traits like idempotency or side effects.

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 sentence that includes the action, resource, and key value details. It is front-loaded and contains no extraneous information.

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 tool with no parameters and no output schema, the description covers the essential information (what it gets and the value range). It could mention the purpose of the calibration value in broader context, but completeness is adequate.

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 no parameters (0 params), so the baseline is 4. The description adds value by specifying the return type (UINT16) and range (0–2000) with a default of 0, which goes beyond the empty 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 'Get' and the resource 'adc_vrefint_calibration'. It explains that it retrieves the factory calibration value for the ADC internal voltage reference, distinguishing it from other getter tools by specific name.

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 explicit guidance on when to use this tool versus alternatives. While there is a sibling setter tool (set_adc_vrefint_calibration), the description does not mention it or provide context for appropriate use.

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