Elements missing a required property

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. The description adds real semantic context beyond the schema: why the empty-string default exists (exporters write '' for "not filled in"), which tells the agent how matching actually behaves. It does not describe return shape or result volume, keeping it below 5.

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 inverse-of-sibling framing followed by the rationale for the default. The clause about exporters is not filler – it justifies a behavioral default the agent might otherwise override.

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 8 parameters, full schema coverage and no output schema, the description covers the key conceptual gap (what "missing" means). It stops short of saying what comes back – a list of elements, a count, or grouped results – which an agent would want for an audit query.

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 eight parameters are already documented, establishing a baseline of 3. The description only reinforces the property/type pairing in prose and adds no syntax, format, or interaction detail (e.g. how pset and property combine) beyond what the schema states.

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 operation (find elements with no value for a given field) and explicitly frames itself as the inverse of a named sibling, bim_elements_by_property. An agent can distinguish it from that sibling and from bim_elements_by_type 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?

Gives a clear use case ("the one most model-audit questions reduce to") and names the complementary tool it inverts, which routes selection. It does not state explicit exclusions or when to prefer a different audit tool such as bim_property_values, so it falls short of a 5.

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