Isolate Layer

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

The description states that the tool hides layers, but does not mention any side effects (e.g., reversibility, viewport-specific behavior, or what happens to previously hidden layers). Annotations indicate readOnlyHint=false, confirming modification, but the description adds minimal behavioral context beyond that.

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 a single, efficient sentence that conveys the core functionality without any wasted words. It is appropriately sized and front-loaded.

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 simple tool with one parameter and an output schema (as per context), the description is mostly complete. However, it lacks handling for edge cases like missing layer names or error conditions. Given the low complexity, this is adequate.

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 covers the parameter fully with a description that aligns with the tool's purpose. Schema coverage is 100%, so baseline is 3. The description does not add significant extra meaning beyond 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's purpose: hiding all layers except the specified one. The term 'layer isolation' is a standard CAD concept, distinguishing it from sibling tools like layer_hide and layer_show that affect single layers.

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 no guidance on when to use this tool versus alternatives (e.g., layer_hide, layer_freeze). There are no explicit conditions or exclusions, which is a significant gap given the many layer-related sibling tools.

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