Construction: Clear (delete scaffold)

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

Annotations already declare destructiveHint=true, so the destructive nature is known. The description adds 'Idempotent' and the sequencing requirement, which are valuable behavioral details beyond what annotations provide. No contradictions.

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?

Two sentences, front-loaded with the action, no wasted words. Every sentence adds value: action, idempotency, and usage order.

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?

The description covers the core action, idempotency, and order dependency. However, it doesn't clarify whether the 'layer' parameter changes which layer is cleared or always clears CONSTRUCTION, creating a slight ambiguity. Also lacks mentions of prerequisites like needing an open drawing, but that is somewhat assumed.

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 coverage is 100% with the parameter 'layer' described as 'Layer to clear'. The description doesn't add new meaning beyond the schema, only mentioning the CONSTRUCTION layer in the action. Adequate but no extra value.

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 'Delete every entity on the CONSTRUCTION layer' with a specific verb and resource. It distinguishes itself from siblings like construction_xline (creates) and drawing_finalize (finalizes), leaving no ambiguity.

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 explicitly states 'Must be called before drawing_finalize to satisfy construction_left critique', providing clear when-to-use guidance. It doesn't discuss when not to use or alternative methods, but the context is sufficient for a cleanup tool.

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