create_room

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

No annotations are provided, so the description carries full burden. It discloses that rooms require enclosed areas and that auto-placement occurs if no location is given, but it fails to explain error handling, permission needs, side effects, or the return value. For a mutation tool, this is insufficient.

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 relatively compact and front-loaded with the core purpose. The Args list is slightly redundant with the schema but adds context. It could be more concise, but overall it is well-structured.

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?

The tool has no output schema, but the description does not explain what is returned after creation (e.g., room ID). It also omits error conditions like invalid level or location outside enclosure. Given the complexity (4 params, nested object), this is incomplete.

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 0%, but the description adds significant meaning: it specifies level_name as the target level with an example, location as an optional point with x,y in mm, and names/numbers with examples. It also explains auto-placement when location is omitted, which is not evident from 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 clearly states the tool creates a room in the Revit model at a specified level. It specifies the verb 'create', the resource 'room', and the context 'Revit model', which distinguishes it from sibling tools like create_detail_line or create_dimensions.

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?

The description mentions that rooms must be placed inside enclosed areas bounded by walls or room separation lines, implying a prerequisite. However, it does not explicitly guide when to use this tool versus alternatives like create_room_separation, nor does it state when not to use it.

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