delete_list

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

The description labels the tool as 'Destructive' and requires confirmation, which provides basic behavioral context. However, given no annotations, it lacks details on side effects, reversibility, or what happens to associated data.

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?

Extremely concise: two sentences, front-loaded with 'Destructive', no unnecessary words. Efficient for its content.

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 no output schema and no annotations, the description is minimal. It covers the action and key parameter but omits success/error details, prerequisites, or post-conditions. Adequate for a simple delete but not comprehensive.

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 the description does not need to add much. It reiterates the confirm_delete requirement, which is already in the schema. No additional semantic 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 clearly states it deletes a contact list from SendGrid, with a specific verb 'delete' and resource 'contact list'. It distinguishes from siblings like update_contact_list or delete_contacts.

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 mentions the required confirm_delete parameter, indicating when to use it, but does not explicitly state when not to use it or compare to alternatives like delete_contacts or delete_segment.

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