pressure_convert

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only repeats parameter names and descriptions from the schema. It does not mention return format, error handling (e.g., invalid units), or any side effects, providing minimal insight into the tool's behavior.

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 concise (two sentences plus parameter list) and front-loaded with the purpose. It avoids unnecessary words. A slight improvement could be using bullet points for readability, but it remains efficient.

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 the simplicity of the tool and the existence of an output schema, the description is adequate but not complete. It lacks error handling context, unit constraints, and does not distinguish from similar siblings. For a 3-parameter tool with no enums in schema, more could be done to ensure confident 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?

The description adds brief explanations for each parameter (value as 'Pressure value to convert', from_unit and to_unit as source/target), and the first sentence lists the supported units. However, with 0% schema description coverage, it does not fully compensate (e.g., missing case sensitivity, allowed unit values explicitly enumerated). The added value is moderate.

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 clearly states the verb 'Convert' and the resource 'pressure units' with a list of supported units (psi, bar, kPa, atm, mmHg, Pa). However, it does not differentiate from sibling tools like 'pressure_calc' or other unit converters, missing an opportunity to clarify unique use cases.

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 guidance is provided on when to use this tool versus alternatives (e.g., 'pressure_calc' or other converters). There are no prerequisites, constraints, or scenarios mentioned, leaving the agent to infer usage without clear direction.

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