calculate_ideal_gas

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

No annotations present, so description carries full burden. It states the constant R=8.314 and that it returns {error}, but does not explain what happens on success, the actual output format (e.g., returns computed value), error conditions, or whether it is read-only. This is insufficient for a tool with no annotations.

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?

Two sentences, no filler. Front-loaded with the equation, then usage constraint, then pointer to related tools. 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?

Has output schema so return structure is covered elsewhere. Description covers the essential usage rule (any 3 params) and points to related bundles. Lacks mention of what happens if fewer than 3 are provided, but overall adequate for a simple calculator with a well-known formula.

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 coverage is 100% and provides basic descriptions. The description adds the crucial rule that exactly 3 parameters must be provided, which is not in the schema. Also provides the gas constant R=8.314, giving context for the equation.

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?

Clearly states the tool solves the ideal gas law (PV=nRT) with the equation named, specifies the four parameters, and the verb 'solve' accurately describes the action. Distinct from hundreds of 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?

Explicitly instructs the user to provide any 3 of the 4 parameters, which is critical for correct use. Mentions related 'science' calculators via list_bundles, but does not specify when not to use this tool or provide exclusion criteria.

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