Resume a paused link

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

The annotations already declare this is not read-only and not destructive, but the description adds substantial context beyond them: changes propagate to taps in about 30 seconds, confirm behaves as a preview without it, policy-disabled links are ineligible, and slug conflicts must be handled first.

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 front-loaded with the core action ('Write. Turns a paused link back on') and then layers in the confirm semantics and edge cases. It is dense but each sentence carries useful operational detail; the final list_links sentence is helpful but slightly auxiliary.

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?

There is no output schema, but for a non-destructive mutation tool the description covers the action, required confirmation, preview behavior, propagation timing, policy restrictions, and slug-conflict resolution. Nothing essential for correct invocation is missing.

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 the schema already documents both slug and confirm. The description still adds meaning beyond the schema by explaining that without confirm nothing changes and that the preview looks up the link among paused links, which clarifies the practical effect of the confirm flag.

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 states a specific verb and resource: 'Turns a paused link back on.' It clearly distinguishes this from siblings such as pause_link and deactivate_link by focusing on resuming a link that is already paused.

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?

It explicitly says confirm: true is required and that omitting it yields a preview. It also names blocking conditions: policy-disabled links cannot be resumed, and slug conflicts must be resolved by pausing or renaming the other active link. It even points to list_links with status: paused as the discovery path.

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