delete_action_public_link

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

With no annotations provided, the description carries the full burden. It mentions deletion but does not disclose permanence, side effects (e.g., cache invalidation), or error scenarios (e.g., link not found, permission denied). The phrase 'delete' implies destruction but lacks detail.

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 a single, concise sentence (12 words) that front-loads the verb and resource. Every word carries meaning; there is no fluff.

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 tool has no output schema, so the description should inform the agent about return values or response behavior. It does not. Additionally, it omits information about idempotency, error handling, and necessary permissions, leaving gaps for a deletion 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?

The schema describes the single 'id' parameter as an integer representing the action ID. The description adds no extra meaning beyond the schema. Since the schema coverage is sufficient for the single parameter, a baseline score of 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 the action ('Delete') and the resource ('public sharing link from an action in Metabase'). It effectively distinguishes from sibling tools like 'delete_action' (deletes the entire action) and 'create_action_public_link' (creates a link).

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 provides no guidance on when to use this tool versus alternatives (e.g., delete_action) or prerequisites (e.g., the link must exist, user needs permissions). No context on when it is appropriate or when to avoid it.

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