calculate_burst_pressure

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

No annotations are provided. The description discloses the formula and tolerance used, but does not mention edge cases, assumptions, output format, or any required permissions. It adds some context but lacks full behavioral detail.

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 moderately concise: a one-line purpose, the formula in LaTeX, and a list of parameters. It is well-structured but could be slightly more streamlined without losing clarity.

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?

The description covers the formula and parameter meanings but does not explain the output or differentiate from similar siblings. Given the tool's simplicity and existence of an output schema, the description is adequate but not fully complete.

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?

With 0% schema description coverage, the description compensates by providing brief descriptions and units for each parameter (e.g., 'Minimum yield strength (psi)'). This adds meaning beyond the schema titles and types, though it does not cover ranges or constraints.

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 tool calculates internal burst pressure using Barlow's formula with API 12.5% tolerance. It includes the verb 'calculate' and the specific resource, which distinguishes it from many sibling calculation tools.

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?

The description implies the tool is for burst pressure calculation using a specific formula, but it does not explicitly state when to use it over alternatives or provide any context about prerequisites or exclusions.

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