bulk_delete

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

Describes soft-delete vs expunge, the irreversibility of permanent deletion, confirm requirement, and dryRun behavior. Annotations already mark destructiveHint=true; description adds critical context like lag in match searches and that permanent deletion is irreversible with no Trash recovery.

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 a single compact paragraph, front-loading the core purpose and then methodically covering conditions. Every sentence adds value without redundancy. Could be structured as bullet points but current form is efficient and clear.

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 but 6 parameters with nested objects, the description covers all essential behavioral aspects: deletion methods, permanence, confirmation, dry-run preview, and safety warnings (content lag). An agent has complete information to invoke 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?

Input schema has 100% coverage, but description adds significant meaning: mutual exclusivity of uids/match, safety trade-offs, the need for confirm when permanent, and dryRun usage. This provides actionable guidance beyond enum values or basic types.

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 multiple messages in one operation' and specifies the two mutually exclusive inputs (uids or match), default soft-delete behavior, and permanent deletion conditions. This distinguishes it from single-message delete tools and other bulk operations.

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?

Explicit guidance: 'Provide EITHER uids OR match.' Further explains that explicit UIDs are safer for destructive cleanup due to content match lag, and dryRun previews without deletion. Also requires confirm: true for permanent deletion, providing clear when-to-use and safety constraints.

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