get_adc_tempsensor_calibration110

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

No annotations exist, so the description carries the burden. It discloses the data type (UINT16), range (0–2000), and default (0), which are key behavioral traits. It also implies read-only via 'factory calibration'. However, it does not explicitly state it is non-destructive or safe, which would warrant a 5.

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 front-loads the purpose, followed by essential metadata in brackets. No extraneous words—every element is necessary and efficient.

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 no output schema and zero parameters, the description is sufficiently complete for a simple getter. It explains what is returned and its constraints. It does not explain the value's use case, but that is acceptable domain knowledge. Minor gap: no mention of whether the value is persistent or requires calibration.

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 0 parameters, and schema description coverage is 100%. The description adds value by specifying the return type and range, which are not in the schema. Baseline for 0 parameters is 4, and the description meets this.

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 retrieves the ADC temperature sensor calibration value at 110°C, specifying it's factory calibration. The verb 'Get' combined with the resource name makes the purpose unambiguous, and the temperature specification distinguishes it from sibling tool get_adc_tempsensor_calibration30.

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 usage guidance is provided, but the context is clear: use when you need the factory calibration value for 110°C. The description does not mention when not to use it or alternative tools, so it relies on the agent's domain knowledge. This is acceptable for a simple getter but could be improved.

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