unlink_source_record

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

Discloses soft-delete (non-destructive) and idempotent behavior in absence of annotations. No mention of permissions, rate limits, or other side effects, leaving gaps.

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 efficient sentences, front-loaded with action. No unnecessary words, though could be slightly more structured with bullet points.

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?

Covers main purpose and idempotency for a simple tool with 2 params and no output schema. Missing details on return value beyond status code, but acceptable given simplicity.

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 covers 100% of parameters with descriptions. Description repeats UUID identifiers without adding new meaning, so baseline 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?

Clearly states it soft-deletes a link between an AnchorID and a source record, distinguishing it from 'link_source_record'. Verb and resource are specific, and idempotency is noted.

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?

Implies use for unlinking without permanent deletion, and mentions idempotency, but lacks explicit when-to-use or when-not-to-use guidance compared to siblings like 'guard_write'.

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