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

Annotations already establish readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds behavioral value beyond annotations by explaining that 'fan' means fan/convection Celsius and that the output includes the nearest gas mark rather than a precise gas-mark equivalent.

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 three short sentences with the main action front-loaded and no redundant restatement of the title or schema. Every sentence adds useful information, and the source URL is a minor but harmless addition.

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 two-parameter, read-only converter with full schema coverage and an output schema, the description is complete: it defines the input scales, clarifies ambiguous abbreviations, and lists the return values. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description meaningfully expands on the schema by decoding each scale enum value: 'c' is conventional Celsius, 'fan' is fan/convection, 'f' is Fahrenheit, and 'gas' is a UK gas mark. It also reinforces the 1–9 gas-mark constraint from the schema's conditional rule.

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 opens with a specific verb and resource: 'Convert an oven temperature,' which immediately distinguishes this from the many generic converter tools in the sibling list. It then names the four accepted scales and the four return values, so an agent knows exactly what the tool does.

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 oven-temperature context is implied by the first sentence, and the scale definitions make the intended use fairly clear. However, the description never explicitly states when to choose this over simpler alternatives such as hopi_celsius_to_fahrenheit, nor does it provide when-not-to-use guidance.

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