autocad_draw_room

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

Annotations already declare the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false). The description adds some useful structure (two wall loops plus a centered label) but says nothing about what a repeated call does, whether geometry is appended or replaces existing entities, or document-state requirements.

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?

Purpose is front-loaded in the first sentence and the Args/Returns layout is scannable with no filler. The Returns block is somewhat redundant since an output schema exists, but the overall size is proportionate to an 8-field tool.

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 a moderately complex drawing tool the description covers geometry and inputs adequately, and return values are handled by the output schema. However, it is silent on document/connection prerequisites, layer auto-creation behavior, and duplicate-draw semantics, leaving real operational 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?

The description enumerates all eight nested fields with types and defaults, but this largely restates the properties already documented inside DrawRoomInput in the schema (the 0% coverage signal reflects the shallow top-level 'params' wrapper). It adds no format, unit, or constraint semantics beyond the schema, so it neither compensates meaningfully nor subtracts.

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: 'Draw a rectangular room: outer + inner wall loops and an area label.' This clearly distinguishes the composite room geometry from generic siblings like autocad_create_line or autocad_create_polyline, though it does not explicitly contrast with the closest sibling autocad_draw_wall.

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 on when to use this instead of autocad_draw_wall, autocad_create_boundary, or manually composing lines/polylines. It also omits preconditions such as needing an open/initialized drawing and connection, so the agent must infer the context entirely.

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