Create elements (any type)

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

Annotations establish the mutation profile (readOnly=false, destructive=false, idempotent=false), and the description adds genuinely new behavior: all items commit in one undo step, failures are per-item and non-fatal, and results come back in input order. It stops short of auth/rate-limit context, so a 4 rather than 5.

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?

Front-loaded with the core purpose and undo behavior, then the item shape, then the fallback guidance. The long inline type enumeration is bulky but does real work in signaling 'any supported type' breadth; only mildly wasteful.

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?

With no output schema, the description correctly supplies the return contract ([{guid, type} | {error}] in input order) and the partial-failure rule. Combined with the routing to type-specific tools for field details, an agent has everything needed to call this 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?

Schema coverage is 100% and the schema itself is thin (items typed only by 'type'), so the description carries real weight by explaining the per-item shape ({type:..., ...fields}) and that fields mirror the type-specific tools' documented schemas. It could note the 'undoName' semantics beyond the schema, hence not a 5.

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?

States a specific verb and resource ('Creates elements of ANY supported type') plus the key scope distinction — a single batch call covering every element type. An agent can immediately tell this apart from the many type-specific create_walls/create_beams/... siblings.

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?

Explicitly routes the agent: 'prefer those [type-specific create_* tools]: they document every field.' This is a direct when-to-use-this-vs-alternatives instruction, which is rare and valuable given how many sibling create tools exist.

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