Convert a single engineering value

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

Annotations indicate read-only safe operation. Description adds value by detailing return structure (exact value, display-rounded, derivation, confidence), which goes beyond annotations. No contradictions.

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?

Description is informative and well-structured: first sentence states purpose, then lists kinds with examples, then return structure. Efficient but packs necessary detail.

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?

Despite no output schema, description explains return values and derivation method clearly. Covers all kinds and parameter constraints. Could mention error handling or edge cases, but overall complete for typical use.

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 covers 75% of parameters with descriptions. Description adds context: explains each kind, gives examples, and clarifies that value is required except for thread. This compensates for the schema's lack of description for the 'kind' parameter.

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?

Description clearly states it converts engineering values between metric and imperial, lists specific kinds with examples, and distinguishes from sibling tools like convert_text (text conversion) and lookup_thread (thread lookup).

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?

Description provides clear context on when to use (for engineering conversions) and lists supported kinds, but does not explicitly state when not to use or suggest alternatives, though sibling tool names provide implicit guidance.

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