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

No annotations are supplied, so the description carries the full disclosure burden. It correctly frames the tool as a value transformation, which implies a side-effect-free computation, but it says nothing about the optional-target behaviour, rounding/precision, or invalid-input handling. Adequate for a trivial pure function, thin for a no-annotation 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 front-loaded sentence with no filler, preamble, or redundancy. Every word (verb, resource, unit set) earns its place.

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?

An output schema exists and the input schema is fully documented, so return values and parameters need no restatement. The description is nevertheless minimal for a tool with zero annotations, and the optional 'to' semantics are left entirely to the schema rather than being surfaced where an agent reads first.

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%, including the enum values and the 'Must be finite and non-negative' constraint, so the schema already does the heavy lifting. The description only repeats the unit list already present in the enums and adds no syntax, default, or edge-case meaning. Baseline 3 applies.

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 gives a specific verb (convert), a precise resource (tyre pressure value), and the exact unit set (PSI, bar, kPa). This uniquely separates it from the sibling converters for distance, speed, power, torque, and fuel economy without the agent needing to open any schema.

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 explicit when-to-use or when-not-to-use statement, and no reference to the sibling converters. Usage is implied by the tightly bounded domain (only pressure units), which is enough for an agent to route correctly, but nothing is stated that helps it choose this over a neighbouring conversion tool.

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