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

No annotations are provided, so the description carries the full behavioral burden. 'Number discarded' and the schema's repeated 'discarded after the check' hints weakly suggest a non-mutating shape check, but the description never states what is validated, what is returned, or that all nine parameters are independent shape checks. The headline claim about unit conversion actively misleads.

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 short but under-specified rather than concise, and it is front-loaded with a misleading claim. Brevity does not earn credit when the content is wrong.

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?

A nine-parameter tool with no annotations, no output schema, and an opaquely named 'rod-m' identifier gets essentially no descriptive support. Nothing explains the relationship among the nine heterogeneous inputs or what calling the tool accomplishes.

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 each parameter is documented in the schema itself (e.g., 'Git ref name; discarded after the shape check'). Baseline 3 applies; the description adds nothing to parameter meaning and its framing is inconsistent with these params.

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 'Rods to meters, number discarded' describes a unit conversion, but the schema exposes nine string parameters (ref, url, city, feed, host, json, path, zone, query) that have nothing to do with rod-to-meter conversion. The stated purpose is misleading and does not tell an agent what the tool actually does, nor distinguish it from siblings like domain-shape, file-path-ok, or validate-json.

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 no indication of when to use this tool versus any of the ~28 siblings, no prerequisites, and no exclusions. An agent has no basis to select it.

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