Permanently Delete Bundle

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

The description adds a critical behavioral detail beyond annotations: the delete cascades to all entry and tag subdocuments, and 'permanently' reinforces irreversibility. This is valuable context not available from the annotations alone. The lack of confirm parameter explanation is a gap, but the description still meaningfully extends transparency.

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, front-loaded sentence with no filler or redundant information. Every word contributes to the core purpose, making it highly concise and well-structured.

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?

Despite clear purpose and good annotations, the description omits the role of the 'confirm' parameter, which is essential for a destructive operation. Without explaining whether confirmation is required or what happens when set to false, the description is not complete enough for reliable invocation. The cascade detail helps, but the missing confirm semantics is a significant gap.

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 0%, and the description provides no additional meaning for the parameters. The purpose of 'confirm' is completely unexplained—it is unclear whether it is a safety gate that must be true or merely a flag. bundle_id is somewhat implied by 'bundle', but the description fails to clarify the critical confirmation behavior.

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 uses a specific verb phrase 'Permanently delete' and clearly identifies the resource ('a bundle') and the full scope ('plus all entry and tag subdocuments'). This effectively distinguishes the tool from siblings like set_bundle_archived or update_bundle, which offer non-destructive or partial modifications.

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 word 'permanently' implies this tool is for final removal rather than archiving (e.g., set_bundle_archived), and the existence of a sibling archive tool provides context. However, there is no explicit guidance about when to use this tool versus alternatives, nor any prerequisites or exclusions.

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