slipbox_delete_link

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

With no annotations provided, the description carries the burden of disclosure. It adds the behavior that an error is returned if no link exists, which is beyond the schema. However, it doesn't mention other behavioral aspects like reversibility or side effects on notes, so it's minimal but not inadequate.

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 two sentences plus a minimal Args block, with no filler or redundant information. It front-loads the purpose and then gives the key differentiator.

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 tool's simplicity (two params, no output schema), the description covers the purpose, parameter semantics, and key behavioral distinction. It is sufficient for a focused tool.

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 provides only names and types, with 0% description coverage. The description's Args section explains that source_id is the note containing the link and target_id is the note being linked to, adding necessary semantic meaning.

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 opens with 'Delete a specific link from one note to another,' which clearly states the verb, resource, and scope. The 'Unlike slipbox_remove_link' sentence distinguishes it from the closest sibling, clarifying its specific behavior.

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 explicitly contrasts with slipbox_remove_link by noting the error-on-missing-link behavior, which guides the user on when to choose this tool over the alternative. This is a clear usage guideline, though it doesn't mention other tools or prerequisites.

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