organizations_bulk_delete

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

With no annotations, the description fully discloses consequences: irreversible deletion, loss of organizations, custom fields, notes, follow relationships, and potential retention of activity history. Also mentions rate limits for large deletions, providing essential behavioral context.

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 well-structured with clear sections (overview, use cases, warning, best practices, parameter details). It is concise yet comprehensive, with no superfluous information.

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?

The description covers tool purpose, impact, best practices, and parameter format. While it mentions rate limits vaguely and lacks error handling details, it is sufficiently complete for a single-parameter bulk delete tool with no output schema.

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?

Given 100% schema coverage, baseline is 3. The description adds value by clarifying that 'ids' is a comma-separated string and providing an explicit example, which goes beyond the schema description.

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 the resource 'multiple organizations in bulk', distinguishing it from individual delete tools like organizations_delete and from other bulk delete tools (e.g., deals_bulk_delete). It provides a specific purpose with example use cases.

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?

The description explicitly lists scenarios for use (data cleanup, GDPR compliance, etc.) and includes best practices (verify IDs, export backup). However, it does not explicitly specify when to avoid using this tool or mention alternative tools for related tasks.

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