delete_layer

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is known. The description adds no extra behavioral context—it only restates the optional object deletion, which is already detailed in the schema's parameter description. No additional side effects, irreversible consequences, or prerequisites are mentioned.

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 concise and front-loaded with the primary action. It consists of two short sentences (bilingual) with no unnecessary filler. While it could be slightly improved by adding a note about default behavior or alternatives, it is efficient and clearly structured.

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 two-parameter destructive tool, the description, combined with the schema and annotations, is complete. The schema explains the parameters and default behavior, and the annotations convey the destructive nature. The description itself clearly states the core functionality. No output schema exists, so return values are not expected to be documented. It does not mention error cases or prerequisites, but these are not required for a basic tool.

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 100%, and both parameters (name and deleteObjects) are fully documented in the input schema, including the default behavior of deleteObjects. The description does not add any further meaning or context beyond the schema, so the baseline score of 3 applies.

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 function: deleting a layer, with an optional flag to also delete its contained objects. This is a specific verb and resource, and it distinguishes itself from sibling tools like create_layer, list_layers, and delete_objects by focusing on the layer as the target.

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 gives no guidance on when to use this tool versus alternatives such as move_objects_to_new_layer or delete_objects. It does not mention conditions like 'if you want to keep the objects, use move_objects_to_new_layer' or any prerequisites. The only context is the action itself, leaving the agent to infer the appropriate usage.

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