calculate_maasp

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

The description explains the calculation but does not explicitly state that it is a read-only, non-mutating operation. Since no annotations are present, the description carries full burden; it adds the formula but omits behavioral traits like side effects or permissions.

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: a one-line summary, the formula, and a parameter list. Every sentence adds value, and the structure is clear and front-loaded.

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 simple calculation with three parameters and an output schema, the description covers the formula and parameters adequately. It does not describe the output, but the output schema exists. Minor gap: no mention of return type or units of result.

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 provides units and brief explanations for all three parameters, and the formula shows their role. This adds meaning beyond the bare schema names.

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 Maximum Allowable Annular Surface Pressure (MAASP) and provides the exact formula. It defines the verb (calculate) and the specific resource (MAASP), differentiating it from 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?

No guidance on when to use this tool versus alternatives like calculate_hydrostatic_pressure or calculate_ecd. There are no explicit when-to-use or when-not-to-use instructions.

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