Elements with no material assigned

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. Beyond that, the description discloses non-obvious internal behavior: plain material, material list, layer set, profile set and constituent set associations are all resolved before the check, which tells the agent it will not get false positives from layered or constituent-based assignments.

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 qualifying condition, and the enumeration of material association kinds is dense but earns its place by defining the predicate. Slightly wordy for what could be a single clause, but no 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?

For a read-only, no-output-schema query tool with five optional filters, the description supplies the semantic definition an agent needs and points at the most useful filter. It omits return shape (element list contents) and any result-size limits, which is a modest gap given there is no output schema.

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%, so all five filters are already documented in the schema, and the description only elaborates on `type` (its role in scoping the query) with an example. That is a genuine but small increment over structured data, matching the baseline 3.

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 resource (elements unreachable by IfcRelAssociatesMaterial) and defines the exact predicate that makes an element qualify, which goes well beyond restating the title. It does not explicitly contrast itself with the near-identical sibling bim_elements_missing_property, so an agent must infer that this is the material-specific variant.

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?

"Restrict with `type` to ask the question that actually matters, e.g. only IfcWall and IfcSlab" gives concrete usage advice on narrowing scope. However, it never says when to choose this tool over bim_elements_missing_property or how to combine it with storey/name filters, leaving alternatives unaddressed.

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