ifcx_create_element

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

With no annotations, the description must disclose behavioral traits. It only describes the creation action but omits side effects (e.g., persistent changes to the IFC model), required permissions, or output format. No mention of what happens on errors or validation.

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?

The description is a single sentence, concise with no fluff. However, it could be restructured to front-load key details or break into bullet points for clarity. Adequate but not optimal.

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?

Given the complexity (12 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain the return value, how to use nested objects (placement, material), or provide examples. The high number of siblings demands more context.

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 0%, so description should compensate. It adds meaning for a few parameters (class, name, properties, material, placement) but ignores many others (sessionId, typePath, attributes, quantity, childName, path, etc.). Incomplete coverage for a 12-parameter tool.

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 clearly states the verb 'Create' and resource 'typed element occurrence', listing included components (class, name, properties, material, placement). It distinguishes from siblings like 'ifcx_create_type' or 'ifcx_instantiate_type' by focusing on element occurrence, though not 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?

No guidance is provided on when to use this tool vs alternatives (e.g., ifcx_instantiate_type, ifcx_add_spatial_structure). No prerequisites, typical use cases, or exclusions are mentioned, which is critical with many similar sibling tools.

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