calculate_ph

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

With no annotations provided, the description carries full burden for behavioral traits. It discloses that the tool returns the missing value and acidity class, and gives the formula. However, it does not mention side effects, permissions, or whether it is safe/read-only. For a calculator, this is adequate but not rich.

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 a reference to list_bundles. It front-loads the purpose and formula, with no unnecessary words. Every sentence adds value.

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 tool's simplicity (2 params, no required, with an output schema), the description is complete. It explains the purpose, usage context, formula, and what is returned. The mention of list_bundles provides further context for related tools.

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 input schema has 100% description coverage for both parameters, but the description adds meaningful context: the relationship between pH and H+ concentration, the formula, and the fact that only one input is needed. It goes beyond the schema by explaining the logic of the calculation.

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's purpose: compute pH from H+ concentration or vice versa. It specifies the formula and mentions use cases (chemistry, aquarium care), making it highly specific. While it does not explicitly differentiate from siblings, the verb 'compute' and resource 'pH' are unique enough among the many calculators.

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 provides context for when to use the tool (chemistry or aquarium care) and directs users to list_bundles for related 'science' calculators. However, it does not explicitly state when not to use it or offer exclusions, so it falls short of a perfect 5.

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