delete_design

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

Explicitly labels the action as 'Destructive' and 'permanently delete', disclosing the irreversible nature. With no annotations, the description appropriately warns about the destructive effect.

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 short, front-loaded sentences with no wasted words. 'Destructive' immediately signals risk. Every sentence earns its place.

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 simple operation (delete by ID with confirmation), the description covers the core purpose and safety precaution. Could mention return behavior or error states, but not essential for a delete 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 coverage is 100%, so baseline is 3. The description adds no new semantic meaning beyond what the schema already provides for both parameters; it merely restates the confirm_delete requirement.

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?

Description clearly states the tool permanently deletes a SendGrid Design Library design, using specific verb and resource. It distinguishes from siblings like delete_template and delete_contacts by specifying 'Design Library design'.

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?

No guidance on when to use this tool versus alternatives such as update_design or other delete operations. Only mentions a requirement (confirm_delete) without context of when deletion is appropriate.

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