bulk_delete_accounts

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

Annotations already mark it as destructive; description adds 'High blast radius.' However, there is inconsistency: description says 'bulk delete' and 'many records,' but the input schema only accepts a single integer 'ids,' making behavior unclear.

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 includes a header with emoji and route, followed by two sentences, but ends with a redundant 'Delete an existing account' which contradicts 'bulk.'

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?

Lacks details on how to delete multiple records (e.g., repeat calls or accept array), no output schema info, and does not clarify return value or side effects beyond blast radius recommendation.

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% but the description does not explain how a single integer 'ids' enables bulk deletion; it contradicts the schema by implying multiple records can be deleted with one parameter.

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 verb 'delete' and resource 'accounts', and emphasizes 'bulk delete' and 'Deletes many records in a single call,' distinguishing it from single-delete siblings like 'delete_an_account'.

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 caution with 'High blast radius — always confirm before calling,' but lacks explicit comparison to alternatives or when not to use (e.g., for single deletions).

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