cad_layer

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say which actions are destructive (delete/rename vs. isolate/restore), what happens to entities on a deleted layer, or whether changes can be undone via cad_undo.

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?

A single compact sentence that front-loads the action and resource with no filler. It is well-structured, though it spends its limited budget restating the enum rather than clarifying behavior.

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 destructive, non-idempotent mutation tool with no output schema, 0% parameter documentation, and a nested properties object, the definition is far too thin. An agent cannot determine action-specific parameter requirements, side effects on drawing entities, or reversibility.

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% and there are 4 parameters including a nested properties object with eight sub-fields. The description only echoes the action enum values and never explains how 'name' vs 'newName' pair with specific actions, or what the nested properties (frozen, locked, colorIndex, etc.) do.

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 pairs a set of specific verbs (create, update, delete, rename, set current, isolate, restore) with a clear resource (drawing layers), so an agent immediately knows the domain. However, it offers no differentiation from sibling tools such as cad_edit or cad_draw, which could plausibly also mutate layer-related state.

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 sentence lists available actions but never states when to choose this tool over cad_edit, cad_draw, or cad_undo, nor does it describe prerequisites such as needing an active document or existing layer. Usage is only inferable from the action list.

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