convert_speed

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

No annotations. The description does not disclose supported units, rounding behavior, or error handling. Users are left to guess valid inputs for 'from' and 'to', which is a significant gap for a conversion tool.

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?

A single sentence, very concise. However, it could include a list of supported units without losing conciseness. Still appropriate for a simple tool.

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 no output schema and 0% parameter descriptions, the description is insufficient. It does not specify what speed units are accepted, making it incomplete for reliable agent invocation.

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 has 0% description coverage. The description adds only the concept of speed but does not specify valid unit strings or expected formats. It fails to compensate for the schema gap.

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 'Convert between speed units' clearly states the tool's function with a specific verb and resource. It distinguishes itself from sibling convert tools (e.g., convert_weight, convert_length) by specifying speed.

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 guidance on when to use this tool versus alternatives. While the name implies it's for speed, explicit context or exclusions (e.g., not for other units) is missing. Adequate but lacks proactive differentiation.

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