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

With no annotations provided, the description carries the behavioral disclosure. It clarifies the destructive scope ('only the wiring between them is removed', 'nodes themselves stay') and a guard condition ('Rejects mutations against published flows'). It doesn't mention reversibility or permissions, but the most important behaviors are disclosed.

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 three sentences with no filler. It front-loads the action, then adds scoping, usage examples, and a constraint. Every sentence earns its place.

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 simple two-parameter deletion tool, the description covers what is removed, what is preserved, when to use it, and a critical failure condition. It doesn't describe the return value or reversibility, but those are not essential for an agent to invoke the tool correctly.

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 compensate. It adds conceptual meaning by explaining that an edge is a connection between nodes and that the operation happens within a flow, which maps to edgeId and flowId. However, it doesn't explain how to discover or format these IDs, leaving some ambiguity for the agent.

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 action ('Remove a single edge'), names the object ('edge/connection'), and explicitly distinguishes itself from node deletion by saying 'nodes themselves stay'. This makes the tool's purpose immediately clear and differentiates it from siblings like delete_node.

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 provides explicit usage triggers with natural-language examples ('disconnect the welcome from the discount') and a key constraint ('Rejects mutations against published flows'). It doesn't name sibling alternatives explicitly, but the usage context is strong enough to guide an agent.

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