Retag or move many links at once

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

Annotations already mark destructiveHint=true. The description adds context: 'rewrites many records at once', the two modes of replace_tags, and the need for confirmation token. This goes beyond the annotation but could mention error handling or idempotency for a fully transparent view.

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 sentences, front-loaded with purpose, no wasted words. Each sentence adds distinct value: purpose, trade-off, and behavioral nuance. Excellent structure.

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?

The description covers the core behavior and the need for a confirmation token, but it omits any mention of the return value. Since no output schema exists, the agent lacks expected response format, success indicators, or error reporting – a notable gap for a destructive bulk operation.

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% – every parameter already has a detailed description. The tool description restates the behavior (replace vs. add, confirm token lifecycle) without adding new meaning beyond what the input schema provides. Baseline 3 is appropriate.

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 clearly states it applies the same tag list and/or target collection to a set of links, and explicitly contrasts with 'one update_link per link' – a specific verb-resource combination with sibling differentiation.

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?

Provides explicit guidance: 'Cheaper than one update_link per link, but far blunter' gives when to use this vs alternatives, and explains the confirmation token requirement for destructive batch operations.

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