ifcx_preview_created_model

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'compose and return' without stating whether the operation is read-only, whether it modifies state, or any other side effects. This is insufficient for a tool that might interact with model state.

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, which is concise but at the expense of necessary detail. It is not well-structured for use by an agent as it lacks elaboration on input or output.

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 no output schema and 0% parameter documentation, the description omits what the returned 'tree/scene summary' looks like (format, structure). In the context of many sibling tools, this is incomplete for an agent to choose and invoke 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?

The sole parameter sessionId is not mentioned in the description. With 0% schema description coverage, the description should clarify its purpose and expected format, but it does not. No value added 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?

The description 'Compose and return viewer-shaped tree/scene summary' vaguely indicates the tool produces a summary for a viewer, but 'viewer-shaped' is unclear. It differentiates from similar siblings like ifcx_spatial_summary or ifcx_export_preview_* only by implication, lacking specificity.

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 guidelines on when to use this tool versus alternatives such as ifcx_spatial_summary or the export preview tools. The context signal shows many siblings, but the description offers no comparison or usage context.

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