set_adc_tempsensor_calibration30

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

The description discloses the value range and default but does not explain the behavioral effect of setting this calibration value, such as whether it is persistent, requires a reboot, or impacts sensor readings. With no annotations, this leaves a significant gap in understanding the tool's impact.

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 with appended range/default info, concise and to the point with no unnecessary words. It is efficiently structured.

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?

Given the simple single-parameter tool and no output schema, the description covers the basic purpose and parameter constraints. However, it lacks details on persistent storage, reboot requirements, or safety implications, making it only moderately complete.

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 provides 100% coverage with min/max and description. The tool description adds the default value '0' and type 'UINT16', which adds some meaning beyond the schema. However, it largely repeats schema information.

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 tool sets the ADC temperature sensor calibration value at 30°C, specifically for factory calibration. It distinguishes from siblings like set_adc_tempsensor_calibration110 by including the temperature point, and from other set_ tools by naming the specific calibration parameter.

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 implies usage for factory calibration but does not explicitly state when to use this tool versus alternatives like set_adc_tempsensor_calibration110 or set_adc_vrefint_calibration. No guidance on prerequisites or context is provided.

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