Delete a link

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

Beyond the destructiveHint annotation, the description reveals that the tool also deletes preserved copies and requires a two-step confirmation flow. This fully discloses the permanent, broad-scope nature of the deletion, which is critical for the agent to invoke correctly.

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?

Two concise sentences, front-loaded with the primary action (deleting a bookmark and copies), followed by the critical two-step behavior. No redundant or irrelevant text.

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 high schema coverage and clear annotations, the description sufficiently covers the tool's purpose and flow. However, it omits details about the return value of the first call (e.g., content of the confirmation token), which could affect correct invocation. Still, the description is largely complete for typical use.

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% with clear parameter descriptions. The description adds value by explaining the two-step workflow and the role of confirm_token in the second call, which is not evident from the schema alone. A minor gap: the format of the confirmation token is not specified, but the schema defines it as a string.

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 the verb 'deletes' and the resource 'bookmark and every preserved copy of the page.' This distinguishes it from sibling tools like bulk_delete_links (bulk deletion) and delete_link_preservations (only preservations), providing precise scoping.

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 explicit guidance on when to use this tool versus alternatives (e.g., bulk_delete_links, update_link). The two-step procedure is explained, but the description does not address context or exclusions, leaving the agent to infer usage from tool names alone.

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