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

With no annotations, the description carries the full behavioral burden, and it does disclose the return shape (compatible and incompatible lists). However, it says nothing about permissions, ID format expectations, or whether results are cached/authoritative. Adequate for a benign read lookup, but thin for a zero-annotation tool.

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, front-loaded with the trigger condition and backed by two short examples, followed immediately by the return description. No filler and nothing to trim.

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?

For a simple two-parameter lookup with no output schema, the description covers the trigger, the output, and a filter option well enough to call it correctly. The main gap is the undocumented material_id expectation, which an agent would have to infer from sibling search 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?

Schema coverage is 50%: process_ids is documented in-schema as an optional filter ('Omit to return all'), while material_id is undocumented anywhere. The description adds no meaning beyond the schema — it does not explain what a material_id is or how process_ids interacts with the result lists.

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 states a specific verb and resource: it returns compatible and incompatible process lists for a given material, reinforced by concrete user-query examples ('can titanium be FDM printed?'). This is clear enough to distinguish it from environment-compatibility siblings, though it never names an alternative tool explicitly.

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?

'Use when the user asks which processes can be used with a material' gives a clear triggering context with two worked examples. It stops short of stating when NOT to use it or naming the sibling (e.g. check_material_environment_compatibility) as the preferred alternative.

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