Delete Layer

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds meaningful behavioral context beyond the annotations by specifying that the layer must have no entities and that Layer '0' is permanently protected, which are important constraints for a destructive operation.

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 two short sentences with no filler. It front-loads the core action and immediately follows with the most critical constraints, making it easy for an agent to parse and act on.

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 single-parameter destructive tool with an output schema and clear annotations, the description covers all essential operational details: the action, the emptiness requirement, and the protected Layer '0'. Nothing necessary for correct invocation is missing.

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 schema already provides 100% coverage for the 'name' parameter, describing it as the layer name to delete and noting it must be empty. The description adds the additional constraint that Layer '0' cannot be deleted, which is not present in the schema and helps agents avoid passing an invalid 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 uses a specific verb ('Delete') and resource ('layer'), and reinforces the core operation with the precondition that the layer must have no entities and that Layer '0' is protected. This makes the tool's purpose unambiguous and distinguishes it from sibling layer tools like layer_modify or layer_freeze.

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 clearly states the conditions under which deletion is allowed: the layer must be empty and Layer '0' cannot be deleted. It does not explicitly name alternatives or when not to use this tool, but the constraints effectively tell an agent when deletion is invalid, which is strong practical guidance for a destructive operation.

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