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

With no annotations, the description carries the full burden of disclosing side effects, but it only states the basic delete action. It does not say whether deletion is irreversible, what happens when the edge does not exist or is not manual, or whether related data is affected. The phrase 'manual edge' adds one useful scoping behavior but falls short of adequate transparency for a destructive operation.

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 one short, front-loaded sentence with no filler or repetition. It efficiently communicates the core operation, though it is terse enough that some of the missing semantics could have been included.

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 destructive tool with no annotations and no output schema, this description is incomplete: it lacks error/edge-case behavior, the role of the optional id parameter, and any mention of what happens to non-manual edges. The sibling list clarifies some context, but the description itself does not provide a complete operational picture.

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 description coverage is 0%, so the description must supply parameter meaning, but it only explains edgeId and says nothing about the optional 'id' property. The required edgeId is described as the deletion key, yet its format and the role of 'id' remain ambiguous. This partially compensates for the schema gap but not enough.

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 states a specific verb ('Delete'), a specific resource ('manual edge'), and an identifier ('edgeId'), which clearly distinguishes it from sibling delete_node, get_edge, patch_edge, and upsert_edge operations. It is not a tautology despite the name, because it narrows deletion to manual edges.

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?

There is no guidance on when to choose this tool over alternatives; the only contextual hint is 'manual edge', which implies non-manual edges are handled elsewhere. It never says 'use model_patch_edge to modify instead' or 'use model_delete_node for nodes'. The agent must infer usage entirely from sibling names.

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