linkding_delete_bundle

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds two facts annotations cannot: contained bookmarks survive the deletion, and the default invocation is a dry-run unless confirm is passed. Those are precisely the behavioral traits an agent needs before calling a destructive tool.

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?

Three short sentences, front-loaded with the action, then the cascade caveat, then the safety switch. Nothing is padded and no sentence is redundant.

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?

For a 2-parameter destructive tool with full schema coverage and no output schema, the description covers action, cascade effect, and the dry-run pattern — enough to call it correctly. It does not describe what the dry-run preview returns or any permission requirements, a minor 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 coverage is 100% and the schema already documents both id and the const-true confirm semantics in detail. The description's 'Omit confirm for a dry-run' restates what the confirm property description says, so it adds no meaning beyond the structured data — baseline 3 applies.

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?

States a specific verb and resource ('Delete a bundle') plus the underlying endpoint, and the clause 'Bookmarks are not deleted' distinguishes its cascade behavior from the bookmark-deletion siblings. An agent can tell exactly what this tool targets without opening the schema.

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?

'Omit confirm for a dry-run' gives clear operational context for how to invoke it safely, and there is no competing sibling for bundle deletion to route against. It stops short of explicit when-not-to-use guidance, keeping it below a 5.

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