archicad_create_room

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description is consistent with that. It adds genuinely useful context beyond the annotations by naming the undo tool as the reversal path and scoping the operation to a single story, though it says nothing about permissions, failure modes, or what happens on an invalid polygon.

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?

Two tightly written sentences, front-loaded with what is created and followed by the reversal instruction. No filler or restated field names.

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?

For an 11-parameter mutation tool with no output schema and only 64% schema coverage, the description is thin: it never mentions the dryRun preview, zone naming/numbering, or thickness/structure options, and there is no indication of what the call returns. The undo hint and story scoping are helpful but do not fill the gaps.

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 description coverage is 64%, so a baseline of 3 applies. The description maps loosely onto the polygon, walls, slab, and story parameters ('outline', 'on one story') but adds no syntax, units, or defaults beyond the schema — notably it never mentions dryRun, zoneName, or the slab/wall thickness options.

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 a room from an outline') and enumerates exactly what gets built — walls along its edges, a floor slab, and a zone, on one story. This composite scope distinguishes it from siblings like CreateWalls, CreateSlabs, and CreateZones, which each build a single element type.

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?

It offers a recovery path ('Revert with archicad_undo'), which is useful, but gives no guidance on when to prefer this composite tool over chaining CreateWalls/CreateSlabs/CreateZones, nor any prerequisites such as needing a valid story from GetStories. Usage is only implied.

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