mindgap_unlink

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

Discloses the destructive action (delete), the return value (removed count and orphaned nodes), and side effects. However, with no annotations, it could further clarify permanence or permissions needed.

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?

Single sentence with no wasted words; all essential information is front-loaded.

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 3-param tool with no output schema, the description covers the action, parameters, and return info well. Could be improved by mentioning when to use this vs. siblings.

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 description explains that src and dst are endpoints and rel is optional, adding some meaning beyond the schema param names. But it does not provide data types, format, or examples, and schema coverage is 0%.

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 (Delete) and resource (edge(s)) between src and dst, and distinguishes from siblings like mindgap_link (which adds edges) and mindgap_remove_node (which removes nodes).

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 guidance on when to use this tool versus alternatives like mindgap_link or mindgap_remove_node. No context on prerequisites or typical usage scenarios.

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