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 disclosing behavior. It claims a conversion operation but gives no indication of what happens to the 10 string parameters, what side effects occur, what the return value is, or why the 'number' is discarded. The description does not explain any actual observable behavior of the 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?

The description is extremely brief, which could be positive, but it sacrifices all meaningful content. It is under-specified rather than concise, and the single sentence does not earn its place because it is inaccurate and unhelpful.

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 10 parameters, no output schema, and no annotations, the description must provide a cohesive explanation of the tool's purpose, inputs, and outputs. It fails entirely: it does not mention any of the schema fields, the expected output format, or how to invoke the tool correctly. The mismatch between description and schema makes this one of the most incomplete definitions possible.

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 the schema description coverage is 100%, each parameter is documented in a way that describes a different tool entirely (e.g., 'Git ref name; discarded after the shape check', 'City name for a public weather hint'). The tool description adds no connection between these parameters and its stated purpose, and 'number discarded' suggests an input that does not exist in the schema. This is not neutral; it is actively harmful to selecting correct parameter values.

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 'US pints to liters, number discarded' is completely unrelated to the input schema, which contains string parameters for git refs, URLs, cities, feeds, hosts, JSON, paths, timezones, queries, and websites. There is no numeric parameter or conversion context, so the agent cannot infer what the tool actually does with any of these fields. This is worse than a tautology because it actively misleads the agent toward a unit-conversion operation that the schema does not support.

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 its many siblings like calc-eval, normalize-url, weather-hint, or validate-json. The description provides no context, prerequisites, or alternative routing, and its irrelevant content only adds confusion.

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