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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description's only behavioral addition is 'Returns: {input}', an unrendered placeholder that conveys nothing, and its unit list actually overstates support (see parameter issues), so it adds little beyond the structured fields.

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?

Front-loaded with the action and unit list, then usage context, then inputs and sibling pointer. Tight overall, though the 'Returns: {input}' fragment is dead weight given an output schema exists.

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 stateless, read-only conversion with full annotations and an output schema, the description covers units, intended domains, inputs and a related-tools pointer. The main gap is the unit list disagreeing with the schema enum, which is a real correctness risk for callers.

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 coverage is 100% and the enums document valid units, so the baseline would be 3. But the description actively misleads: it lists MPa and torr as supported units and names the parameters 'from-unit'/'to-unit' whereas the schema uses 'from'/'to' with an enum lacking MPa and torr, so an agent following the prose could pass an invalid unit.

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 states a specific verb and resource ('Convert pressure') and enumerates the unit set, so the agent immediately knows what the tool computes. However, it never distinguishes itself from the near-duplicate sibling calculate_pressure_convert (nor the other convert_* tools), leaving the agent unable to choose between them on description text alone.

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?

'Use for engineering, tires, weather' gives positive context about when the tool applies. There is no when-not guidance, no mention of the overlapping calculate_pressure_convert sibling, and no note on which unit conventions or rounding apply, so routing guidance is only implied.

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