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. The description 'Joules to calories, number discarded' suggests a pure numeric conversion, but the schema parameters (ref, url, city, feed, host, json, path, zone, query, website) indicate the tool actually performs some kind of multi-purpose validation or hint operation. The description does not disclose what side effects, if any, occur, what gets discarded, or what the tool returns. This is a severe transparency failure.

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 extremely short, which could be seen as concise, but it is under-specified rather than efficiently structured. It front-loads a misleading unit-conversion phrase and provides no useful information. Every word is wasted because the description does not match the schema's actual scope.

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?

Given 10 parameters, no annotations, no output schema, and 30 sibling tools, the description is completely inadequate. An agent cannot determine what inputs to provide, what the tool does with them, what it returns, or how it differs from siblings like calc-eval, citation, or validate-json. The description is missing nearly all contextual information needed for correct 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 description coverage is 100%, so the baseline is 3, but the description itself adds no parameter meaning. The schema descriptions are individually clear (e.g., 'Git ref name; discarded after the shape check'), but the tool description 'Joules to calories, number discarded' does not explain how these 10 unrelated parameters relate to the tool's purpose. The mismatch between the description and the schema actively confuses parameter semantics, so the score is below baseline.

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 'Joules to calories, number discarded' is a tautology that restates the tool name without explaining what the tool actually does. It does not state a clear verb+resource, and the input schema (10 unrelated string parameters like 'ref', 'url', 'city', 'feed', 'host', 'json', 'path', 'zone', 'query', 'website') suggests the tool is not actually a unit conversion tool at all. The description is misleading and provides no differentiation from the 30 sibling tools.

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 guidance on when to use this tool versus alternatives. The description does not mention any of the sibling tools, nor does it explain what scenario would select joule-cal over calc-eval, citation, normalize-url, or any other sibling. The schema's 10 unrelated parameters further obscure the intended use case, leaving an agent with no basis for invocation.

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