Delete Drawing Upload

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description reinforces permanence and adds the 'unreviewed' condition, but does not disclose additional side effects, error conditions, or authorization requirements beyond what annotations and schema provide.

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 relatively short (5 sentences) and front-loaded with the main action. However, there is minor redundancy in repeating 'cannot be undone' and 'permanently removes', which could be tightened.

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 delete operation, the description covers the key aspects: action, target (unreviewed), permanence, required parameters, and endpoint. It does not explain the 'view' parameter's effect (but schema does) or error handling, but given the annotations and simplicity, it is reasonably complete.

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%, so the schema fully documents all three parameters. The description merely restates required parameters ('id, project_id') and the view parameter's enum usage is not elaborated beyond schema. No new parameter meaning is added.

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 unreviewed Drawing Upload' with a specific verb and resource. It also emphasizes permanence and irreversibility, and the qualifier 'unreviewed' distinguishes it from other drawing-related delete tools in the sibling list.

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 implies usage for unreviewed uploads only, but it does not explicitly state when not to use it or suggest alternatives like delete_drawing or delete_drawing_set for reviewed uploads. No exclusions or contextual guidance are provided.

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