disconnect_all

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

With no annotations provided, the description fully carries the behavioral burden. It discloses hard-delete semantics, atomicity with rollback on partial failure, the provenance of edge IDs, and the return shape '{removed: N}', which is exactly the operational context an agent needs.

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 compact and front-loaded, with each sentence adding a distinct piece of information: what it does, when to use it, its atomicity behavior, ID provenance, and return value. There is no redundancy or filler.

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 single-parameter tool with no output schema, the description is remarkably complete. It covers usage context, side effects, failure behavior, input sourcing, and return format, leaving no critical gap for an agent deciding whether and how to invoke it.

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 fully documents the structure of 'items' and 'edge_id', so the baseline is 3. The description adds meaningful semantic guidance by stating that edge IDs come from 'recall' or 'why_connected', and by framing them as 'confirmed edges', which helps the agent populate the parameter correctly.

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 a specific verb-resource pair, 'Batch hard-delete of edges,' which clearly identifies the operation and the object it acts on. It also distinguishes itself from single-edge alternatives like 'disconnect' by emphasizing the batch aspect.

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?

It explicitly states when to use the tool: when there are 2 or more confirmed edges to remove at once. It also positions the tool as more efficient than multiple 'disconnect' calls, giving the agent a clear decision rule.

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