Bulk delete links

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is largely covered. The description adds the useful 100-item cap and the workspace scoping, but says nothing about irreversibility, the confirm requirement, or that non-existent IDs are silently ignored (those live only in the schema).

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?

A single front-loaded sentence with no waste. It is appropriately sized, though it is so terse that it sacrifices some context in the name of brevity.

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 destructive mutation with no output schema, the annotations carry the safety signal and the schema fully covers parameters, so the description is minimally sufficient. It still omits any note about irreversibility or the confirm guard, leaving the agent to read the schema for critical call behavior.

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 account, confirm, and link_ids are fully documented in the schema itself. The description only echoes the 100-ID limit already stated for link_ids, adding no new parameter meaning.

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 ('Bulk delete links') with scope ('up to 100', 'authenticated workspace'). This implicitly separates it from the single-item delete_link and from bulk_update_links, though it never names those siblings explicitly.

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?

No guidance on when to choose this over delete_link (single) or bulk_update_links, and no stated prerequisites beyond the implicit need for authentication. The 'up to 100' limit hints at batching, but the agent must infer when bulk is appropriate.

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