deals_bulk_delete

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

No annotations exist, so description carries full burden. It explains soft-delete vs permanent delete, 30-day recovery window, and recommends caution. It does not mention user permissions or rate limits, but covers core behavior adequately.

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?

Front-loaded with purpose, then structured into workflow tips and use cases. Slightly verbose with examples but every sentence adds value. Could be shorter, but efficient for the complexity.

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 single parameter, no output schema, and no annotations, the description covers purpose, behavior, usage, and caution. Missing details on return value or confirmation, but sufficient for agent to use correctly.

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 covers the 'ids' parameter with description and minItems. Description adds use cases and example JSON, reinforcing usage. With 100% schema coverage, baseline is 3; description adds marginal value beyond schema.

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 deletes multiple deals in bulk, distinguishing it from the singular delete tool. It specifies the action (delete), resource (deals), and scope (multiple, bulk).

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?

Provides workflow tips: use array of IDs, soft-delete first, permanent after 30 days, caution for bulk effects, and suggests getting IDs via list/search. Common use cases are given. No explicit when-not-to-use, but the caution implies careful consideration.

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