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

Annotations already establish read-only, idempotent, closed-world behavior, so the description's job is to add analytical context — and it does: it discloses that results mirror the Glazecalc app and that Stull placements are illustrative rather than predictive, citing the cone 11 fixed-flux test basis and warning the crazed region is not a fit test. That is meaningful interpretive guidance an agent would otherwise get wrong.

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?

Purpose is front-loaded in the first sentence and outputs are enumerated efficiently, but the second half is a sprawling three-clause sentence on Stull caveats that repeats the 'guide, not a promise' idea twice (regions move / not a test of fit). It could be trimmed by a third without losing instruction 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?

There is no output schema, so the description carries the burden of telling the agent what comes back, and it does so by enumerating every reported quantity including the Stull region labels (unfused, matte, semi-matte, bright, underfired). For a computationally complex tool this is close to complete, missing only response shape/structure detail.

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%, covering line structure, material naming, analysis fallback and language tags, so the schema does the heavy lifting. The description adds nothing about the parameters (no clarification of units, colorant exclusion, or language fallback behavior), so baseline 3 applies.

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?

Names a specific verb and resource and enumerates what the analysis produces (unity/Seger formula, oxide groups, silica:alumina ratio, fired analysis, LOI, calculated thermal expansion) plus the Stull output. It does not explicitly distinguish itself from siblings like check_limits or compare_recipes, so it stops short of a 5.

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 Stull paragraph implies this is an interpretive/educational analysis ('a guide to the surface, not a promise') and lists conditions under which the Stull regions are unreliable (cone other than ~11, boron, other fluxes). There is still no explicit statement of when to choose this tool over check_limits, solve_target or compare_recipes.

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