Delete A Drawing Area

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

The description emphasizes irreversibility with statements like 'This cannot be undone' and 'Permanently removes,' which adds context beyond the destructiveHint annotation. It does not contradict annotations, providing supplementary detail about the permanent nature of the 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 somewhat redundant, repeating 'permanently delete/removes' and 'cannot be undone.' It could be more concise, but it front-loads the purpose effectively.

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?

Given the tool's simplicity (2 parameters, no output schema) and the annotations covering destructiveHint, the description adequately covers the basic behavior, irreversibility, and required inputs. It is sufficiently complete for a delete operation.

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 descriptions for both parameters in the schema. The description merely lists required parameters (project_id, id) without adding further meaning, so it meets the baseline but does not enhance understanding.

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 an existing Drawing Area' and specifies that it permanently deletes the associated Drawings. It includes the context of the project and uses a specific verb+resource combination, distinguishing it from sibling tools like update_drawing_area.

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?

It indicates 'Use this to permanently delete the specified Drawings,' implying its usage scenario. However, it does not provide guidance on when not to use it or alternatives, such as other delete operations on drawings or areas.

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