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

Annotations cover the safety profile (readOnly, non-destructive, closed-world), so the bar is lower, yet the description adds real substance: output is caveats-first, each fact is tagged vendor-cited vs general engineering knowledge, and the tool refuses judgment calls. It doesn't discuss freshness, coverage gaps, or latency, but for a static knowledge lookup that is minor.

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?

Front-loaded with purpose and use-case in the first clause, and every sentence carries a distinct obligation (call timing, output shape, judgment boundary, terminology). It is dense with parentheticals and slightly over-packed, but nothing is filler.

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?

With no output schema, the description must convey return content, and it does: caveats-first specs, comparison ladders, finish/coating options, and the epistemic tagging of each fact. Nothing an agent needs to call and correctly relay this tool is missing.

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% and every parameter already documents its own semantics (process enum-like values, free-form material with family behavior, question intent mining). The description reinforces intent but adds no syntax or format detail beyond the schema, 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?

States a specific verb and resource ('material intelligence for material-choice / strength / durability / heat / outdoor questions') and immediately gives the question class it serves, with concrete examples. No sibling tool covers this ground, so an agent can distinguish it without opening any schema.

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?

Explicit timing instruction ('Call it BEFORE answering such a question, then relay the facts') plus an explicit scope boundary (facts only, never fitness-for-purpose or safety guarantees) and even phrasing guidance ('advertised', not 'certified'). When-to-use and when-not-to-overstep are both stated.

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