calculate_metal_combustion_equilibrium

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

With no annotations, the description carries the full burden. It discloses that the tool builds a dynamic mechanism from NASA databases and handles gas and condensed phases, but does not mention side effects, authentication needs, rate limits, or computational intensity. Some behavioral context is present but incomplete.

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 3 concise sentences: purpose, method, supported metals. It is front-loaded and contains no superfluous information. Every sentence earns its place.

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 tool is moderately complex with an output schema, but the description omits usage context, prerequisite (NASA database availability), error conditions, and typical output interpretation. 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?

Schema description coverage is 0% (the tool description does not explain parameters individually). The description only lists supported metals and implies the oxidizer and other parameters, but does not add meaning beyond the schema's property descriptions. Given low coverage, the description should compensate more by summarizing key parameters and 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 equilibrium temperature and products for metal-oxygen/air combustion. It specifies it builds dynamic mechanisms from thermodynamic databases and handles both gas and condensed phases. This distinguishes it from sibling tools like calculate_adiabatic_flame_temperature or equilibrate.

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 usage for metal combustion equilibrium but does not explicitly state when to use this tool versus alternatives like equilibrate or calculate_adiabatic_flame_temperature. No guidance on when not to use or prerequisites is provided.

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