set_adc_tempsensor_calibration110

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

With no annotations, the description carries the full burden. It mentions 'factory calibration' and provides a default, but does not disclose whether writing requires permissions, replaces existing values, or has any side effects. Minimal behavioral insight beyond what the name implies.

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?

Single sentence that conveys the core purpose and includes a parenthetical with type/range/default. No extraneous words, though it repeats the tool name unnecessarily. Efficient but not maximally compact.

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, the description covers the parameter's meaning, type, range, and default. However, it lacks context on the calibration's significance or when to use it. Given no output schema and no annotations, the description is minimally adequate but leaves 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?

Schema coverage is 100% for the single parameter. The description adds the default value (0) not present in the schema, which aids understanding. Although the schema fully captures range and type, the extra default info provides marginal value beyond what's structured.

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 explicitly states the verb 'Set' and the resource 'adc_tempsensor_calibration110', and clarifies it's the ADC temperature sensor calibration value at 110°C. It adds type, range, and default info. However, it doesn't explicitly distinguish from siblings like set_adc_tempsensor_calibration30, but the name alone differentiates.

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, such as set_adc_tempsensor_calibration30 or set_adc_vrefint_calibration. No prerequisites, context, or conditions provided.

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