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

With no annotations, the description carries the full behavioral burden and delivers little: it does not say what the output looks like (a verdict, a list of conflicting pairs, a score), whether the operation is read-only, or how many statements are expected. "Agent outputs" is the only scoping detail provided.

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?

A single short sentence with no waste and the purpose front-loaded, which is structurally fine. However, brevity here borders on under-specification rather than tight writing, so it is merely adequate.

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?

No annotations, no output schema, and a parameter with zero description coverage means the description should explain the interaction contract and the shape of results. It explains neither, leaving the caller unable to predict what a contradiction report contains.

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% for the single `statements` parameter. The description says the input is "agent outputs" but adds no semantics about ordering, count limits, language, or whether each string is an independent claim. The example in the schema does more work than the description.

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?

States a specific verb and resource: "Detect contradictions in agent outputs." The "[agents]" prefix scopes it to agent outputs, but the description does nothing to distinguish it from the near-identical sibling `detect_contradiction`, which appears to cover the same operation. Clear purpose, no sibling differentiation.

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 use this tool versus `detect_contradiction`, nor any precondition such as minimum statement count or whether statements must come from the same agent run. The agent is left to infer usage entirely.

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