confirm_bulk_delete

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the destructive nature (bulk deletion), the human confirmation requirement, and the exact phrase needed. However, it doesn't mention rate limits, error handling, or what happens after confirmation, which are partially covered in the schema but could be highlighted in the description for clarity.

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 front-loaded with critical information (human confirmation requirement) in a single, efficient sentence. It avoids unnecessary details, but could be slightly more structured by separating the confirmation instruction from the automatic call warning for better readability.

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 the complexity (6 parameters, nested objects, no output schema, and no annotations), the description is reasonably complete. It covers the core purpose and usage constraints but lacks details on output behavior or error scenarios. Since there's no output schema, adding a hint about what to expect after confirmation would improve completeness.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal parameter semantics beyond the schema, mainly emphasizing the humanConfirmation requirement. It doesn't provide additional context for parameters like batchSize or options, so it meets the baseline for high schema coverage.

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 explicitly states the tool's purpose: to confirm bulk deletion after human confirmation. It specifies the exact phrase required ('DELETE ALL') and distinguishes it from automatic execution, making it highly specific and clear about its function.

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 explicit usage guidelines: 'DO NOT call this automatically - requires genuine human confirmation.' It also references a sibling tool (preview_bulk_delete) via the confirmationToken parameter, indicating when to use this tool versus alternatives like canceling or selecting individual items.

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