delete_bundle

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

No annotations are provided, so the description must disclose behavioral traits. 'Delete a bundle' does not explain whether deletion is permanent, cascades to associated bookmarks, requires permissions, or is reversible. This is a significant gap for a destructive operation.

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, clear, and appropriately short sentence. Every word earns its place, with no fluff or redundancy, making it highly concise and easily parsable.

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 tool is a destructive delete operation with no annotations, the description fails to convey critical context such as side effects or permanence. While schema and output schema cover parameters and returns, the lack of behavioral disclosure leaves the description incomplete for an AI agent.

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 for parameters is 100%, and the description adds no additional meaning beyond the schema's 'bundle_id' definition. The baseline of 3 applies because the schema fully documents the parameter, but the description provides no extra context.

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 'Delete a bundle' is a specific verb+resource statement that clearly distinguishes itself from sibling tools like create_bundle, get_bundle, and update_bundle. It unambiguously communicates the tool's core 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?

There is no guidance on when to use this tool, no prerequisites or alternatives mentioned, and no exclusions. The description only states the action without contextualizing it relative to other bundle operations or possible edge cases.

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