hydrostatic_pressure

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

With no annotations, the description carries the full burden. It usefully discloses extra return content (pressure gradients, seabed thermocline temperature estimate) and the depth limit, but omits behavioral traits such as whether density is held constant, whether salinity/temperature affect the pressure result, and any precision caveats.

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 dense sentence that front-loads the computed quantity and output units before the secondary extras. Nothing is wasted, though the trailing 'including exact pressure gradients and ambient seabed thermocline temperature estimates' slightly crowds the core statement.

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 one-required-parameter calculator with no output schema, the description covers inputs, output units, and even secondary outputs, which is close to sufficient. It falls short only on the physics assumptions (constant density) and the absence of any usage routing, which are secondary for a deterministic calculation tool.

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%, so the schema already documents unit, depth, and density with defaults. The description adds only the depth range ceiling ('up to 3,500m / 11,500ft'); it adds no unit-conversion or density-override guidance beyond the schema, so baseline 3 is appropriate.

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?

States a specific verb (calculates) and resource (hydrostatic seawater pressure) plus the exact output units (Bar, MPa, PSI) and the input basis (water depth). It does not reference any sibling, but the siblings (dosage, pipe collapse, hydrate equilibrium) are unrelated domains, so confusion is unlikely.

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?

Usage is implied by the domain (deepwater pressure at a given depth) and the stated 3,500m/11,500ft ceiling hints at applicability limits, but there is no explicit when-to-use guidance, no statement of when another tool is more appropriate, and no mention of the tool's assumptions at extreme depths.

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