ifcx_create_spatial_structure

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

No annotations provided, and description gives no behavioral details beyond the name. No disclosure of side effects, required permissions, or consequences of creating a 'tree'.

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?

Single sentence with no waste; front-loads the core action. However, it may be too terse given the complexity.

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?

Description is inadequate for an 11-parameter tool with no annotations or output schema. Missing details on return values, behavior when optional params omitted, and hierarchical constraints.

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, description must compensate but fails. It names hierarchy levels but does not explain any of the 11 parameters (e.g., sessionId, projectId). No clarification of optional vs required beyond the schema.

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?

Description states it creates a project/site/building/storey/space tree, a specific verb-resource combination. However, it does not differentiate from sibling 'ifcx_add_spatial_structure' which may serve a similar role.

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 on when to use this tool vs alternatives like ifcx_add_spatial_structure or ifcx_create_element. No context on prerequisites or typical workflow.

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