ifcx_create_geometry_brep

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

No annotations are provided, so the description must fully disclose behavioral traits. It does not mention any side effects, error conditions, permissions, or what 'attach' means in terms of modifying existing data. This is a significant gap for a mutation 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?

The description is a single concise sentence, which is efficient, but it omits essential details. It is front-loaded with the core action but lacks supporting context, making it minimally adequate.

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 tool's complexity (9 parameters, 2 enums) and lack of output schema, the description is severely incomplete. It does not describe return values, side effects, or parameter relationships, leaving the agent with insufficient information to use the tool correctly.

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?

With 0% schema description coverage, the description should explain key parameters like ownerPath, format, data, encoding, tolerance, and units. It mentions formats but leaves all other parameters unexplained, providing no added value beyond the schema structure.

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 it creates a BRep body tier reference with specific formats like OCCT BREP or STEP AP242. However, it does not differentiate from sibling geometry creation tools such as ifcx_create_geometry_curve or ifcx_create_geometry_mesh, leaving ambiguity about when to use this tool over others.

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?

The description provides no guidance on when to use this tool versus alternatives. With many geometry-related sibling tools, the agent lacks context for selecting this tool over similar ones like ifcx_create_geometry_mesh or ifcx_create_geometry_proc.

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