create_room_separation

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the lines 'act as invisible walls for room calculation' but does not mention whether this operation is destructive, if special permissions are needed, or what side effects (e.g., modification of room boundaries) occur. The description lacks critical details about the tool's impact on the model.

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 well-structured with an Args section, but includes unnecessary details like 'ctx: MCP context for logging' which is not relevant for an agent selecting the tool. The purpose is front-loaded, and the overall length is appropriate, but a few words could be trimmed.

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 3 parameters, the description explains the input well but does not mention what the tool returns (e.g., element IDs, success status). For a creation tool, return value is often needed for subsequent operations. The description is incomplete for full context.

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 input schema has 0% description coverage, so the description must compensate. The Args section explains lines as list of segments with start_point and end_point dicts (x,y,z in mm), and level_name/view_name default to active view. This adds significant meaning, but could be more structured for the 'lines' parameter (e.g., exact format of dict).

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 'Create room separation lines to define room boundaries,' specifying the verb (create) and resource (room separation lines). It distinguishes from sibling tools like create_room and create_grid by focusing on invisible walls for room calculation, making its purpose unambiguous.

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 provides explicit use cases: 'Use these when physical walls don't fully enclose a space (e.g., open-plan areas, corridors).' However, it does not mention when not to use or suggest alternatives, which would be helpful for an AI agent deciding between this and other creation tools.

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