Permanently remove an existing share link so its URL immediately stops working. Confirm the deletion to revoke access to the shared document or resource.
⚠️ DESTRUCTIVE: Permanently delete a share link. The shared URL will stop working.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| confirm | Yes | Must be true to confirm this destructive operation |
Changes observed during successful MCP inspections.
v3.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already include destructiveHint=true, but the description adds concrete context: the deletion is 'permanent' and the shared URL 'will stop working.' This goes beyond the bare hint and gives the agent a clear sense of the irreversible consequence.
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 sentences with a front-loaded destructive warning, followed by the action and its consequence. Every word earns its place; there is no fluff or redundancy.
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 simple two-parameter delete operation without an output schema, the description covers what the tool does and what effect it has. It does not explain return values or all side effects, but those are unnecessary for this straightforward destructive action.
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 50%: only 'confirm' has a description in the schema. The tool description adds no parameter meaning, leaving 'id' undocumented. It does not compensate for the low coverage, but the confirm requirement is adequately covered by the schema.
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 the specific verb 'delete' and the resource 'share link', and clarifies the consequence ('The shared URL will stop working'). This distinguishes it from the many other delete_* siblings by naming the exact resource, so an agent can immediately tell it apart.
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?
The description does not explicitly state when to use this tool versus alternatives like delete_share_link_bundle or when it is not appropriate. However, the action is self-evident from the name and description, making usage guide the implied but not explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.