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

With no annotations, the description carries the full burden and usefully discloses the three categories of results, including cached crossings from prior agents and bridge language containing contrast markers. It does not state read-only status, permissions, or rate limits, but the return behavior is well described.

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 front-loaded with the core purpose and then explains return categories and usage in a logical order. It is mostly efficient, though the phrase 'the most generative graph traversals' is evaluative filler rather than operational detail.

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?

There is no output schema or annotation set, so the description must cover purpose, behavior, and returns, which it does thoroughly. It explains the returned categories and the rationale for cross-stage connections, giving an agent enough to invoke and interpret 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 100%, so the id and limit parameters are already documented in the schema. The description adds no extra syntax, constraints, or meaning beyond what the schema provides, making the baseline score 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?

The description states a specific verb and resource: finding edges from a piece where pieces are in structural opposition rather than similarity. It clearly distinguishes itself from similarity-based search, but it does not explicitly name a sibling tool such as get_connections or traverse.

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 gives a clear usage context: useful when search returns too many similar pieces, because opposition finds the gap. It does not elaborate on when not to use it or name alternative tools explicitly, but the context is actionable.

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