sophos_bulk_delete_mailboxes

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. It states 'Remove multiple mailboxes from email protection' but does not clarify whether this deletes the mailboxes entirely or just removes protection, reversibility, or required permissions. The tool is destructive, but the description lacks necessary cautionary details.

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 sentence of ten words, which is concise. However, it omits important details like return value and error handling, making it under-specified. It earns credit for brevity but not for completeness.

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 tool has no output schema, and the description does not explain what the response contains (e.g., list of deleted mailbox IDs, success status). For a destructive bulk operation, an agent needs to understand confirmation or error handling. The description lacks these details, making it incomplete for reliable invocation.

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?

The input schema has 100% description coverage with minimal explanations (tenant_id: 'Tenant UUID', mailbox_ids: 'Array of mailbox UUIDs to delete'). The tool description adds no additional meaning beyond the schema, so it meets the baseline for adequate but not enhanced parameter semantics.

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 removes multiple mailboxes from email protection in a single request. The verb 'Remove' and resource 'multiple mailboxes' are specific, and it contrasts with sibling tools like sophos_delete_mailbox (singular) and sophos_bulk_add_mailboxes (adds). Context signals indicate it's a bulk operation, further clarifying purpose.

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 provides no guidance on when to use this tool versus alternatives like sophos_delete_mailbox for single deletions, or prerequisites (e.g., tenant admin permissions). There is no mention of when not to use it or related tools, leaving the agent to infer usage context.

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