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

No annotations are provided, so the description carries the full burden. 'Number discarded' is vague and does not disclose what happens to inputs, whether there are side effects, or what the return value is. The parameter descriptions mention 'discarded' for several fields, but that is in the schema, not the tool description.

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 under-specified rather than concise. A few words do not constitute structured guidance for a tool with 9 parameters, and the phrase 'number discarded' is elliptical, not clear.

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 9 parameters, no annotations, and no output schema, the description fails completely. An agent cannot determine what inputs belong with this tool, what action is taken, 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 coverage is 100%, the description does not add meaning to parameters and actively misleads: it promises a Joule-to-calorie conversion while all parameters are strings like 'Git ref name' or 'file path'. No parameter could plausibly express an energy amount.

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 not a clear statement of what the tool does. None of the 9 string parameters (ref, url, city, feed, etc.) relate to joules or calories, so the description is misleading rather than distinguishing.

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 about when to use this tool or when to prefer a sibling. No alternatives are mentioned, and the context signals list siblings like calc-calc and validate-json without any routing hints.

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