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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals nothing about supported unit systems, conversion direction, default behavior, error handling, or output format. The description is behaviorally opaque.

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 only four words, which is brief, but it is tautological placeholder text rather than purposeful conciseness. Every word is wasted repeating the name, and no information is front-loaded because no information exists.

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 tool with three loosely defined string parameters, no annotations, and no output schema, this description is completely inadequate. An agent cannot correctly determine what input to send, what units are supported, or what result to expect.

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?

Although schema description coverage is 100%, the parameter descriptions ('Type to process', 'Unit to process', 'Value to process') are generic placeholders that add no real semantics. The tool description does not compensate by explaining accepted types, unit formats, or how parameters relate, so meaning is still largely absent.

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 'Metric Imperial: Metric Imperial' is a pure tautology that restates the tool name. It contains no verb, no resource description, and no differentiation from the hundreds of sibling conversion tools. An agent cannot tell what operation this tool performs.

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?

There is zero guidance on when to use this tool versus alternatives like cm-to-inches, km-to-miles, or units-convert. No context, preconditions, or exclusions are provided, leaving the agent to guess among many conversion tools.

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