manage_layer

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

No annotations are provided, so the description carries the full behavioral burden for a mutating tool. It says nothing about persistence of changes to the drawing, what happens when 'create' is called on an existing layer, whether frozen/locked states affect later draw calls, or any error conditions. Only the conditional requirement on 'name' hints at behavior.

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 one-line summary is front-loaded and the Args block is scannable with no filler. Every line maps to actual information an agent needs, though it could be slightly tighter about which params apply to which actions.

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?

An output schema exists, so return values need not be explained, and parameter documentation is solid. What is missing for a stateful CAD mutation tool is behavioral context: preconditions per action, effect of freeze/lock on subsequent operations, and whether changes persist to the drawing file.

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 compensates well: it enumerates all valid 'action' values, states the conditional requirement on 'name', gives the ACI range 1-255 for 'color', and supplies concrete linetype examples. What remains unclear is the default 'list' action and how color/linetype interact with the on/off/freeze actions.

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 first sentence names a concrete resource (AutoCAD layers) and enumerates the operations (list, create, switch, change properties), which is far more than a restatement of the name. It is clearly distinct from the draw_* siblings, though it never explicitly says so. The scope statement is specific enough for an agent to pick it over draw_line or modify_entities.

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 Args block implies per-action usage (name is 'required for all actions except list'), which is real guidance. However, there is no statement of when to reach for this tool versus siblings, no preconditions (e.g. must the layer already exist for 'on'/'freeze'/'lock'?), and no note that 'set_current' changes global drawing state.

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