ifcx_compose_world_transform

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

With no annotations, the description carries the full burden but fails to disclose whether the operation is read-only or modifies state, what prerequisites exist (e.g., a valid hierarchy), or any side effects. 'Compose' is ambiguous without behavioral details.

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 front-loaded. It could be improved by adding a brief note on parameters or usage without losing conciseness.

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 three parameters and no output schema or annotations, the description is grossly inadequate. It does not explain what the tool returns, how to construct the input, or any dependencies. The existing siblings offer no additional clues.

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% and the description does not clarify the meaning of 'sessionId', 'stackId', or 'path'. Only 'path' is required and implied to identify the node, but no format or constraints are provided.

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 states the tool 'composes the transform chain and translation for a node,' providing a specific verb and resource. However, it does not differentiate from sibling tools like 'ifcx_set_transform' or 'ifcx_compose_stage', which may perform similar operations.

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 given on when to use this tool versus alternatives such as 'ifcx_set_transform'. The description lacks context on prerequisites or scenarios where composing a world transform is appropriate.

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