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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so safety and repeatability are covered. The description adds useful return semantics ('with both sides of the evidence'), but says nothing about result ordering, truncation, or how the default/maximum limit affects output.

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 front-loaded sentence that carries purpose, scope, and return content without padding. It is efficient, though slightly dense and could separate the optional-filter clause for readability.

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?

With no output schema, the description carries return-value burden and does describe the payload (contested relations plus both sides of evidence). Combined with annotations covering the safety profile, an agent has enough to call it correctly; only limit/pagination behavior is left unstated.

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 schema gives types and bounds only. The description explains the 'entity' filter but adds nothing about 'limit' (why 20 is the default, what happens past 50), leaving half the parameters semantically thin.

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 resource ('relations the Atlas marks as contested or that carry conflicting studies') plus what accompanies it ('both sides of the evidence'), which is far more than a restatement of the name. It implicitly distinguishes itself from the generic sibling find_relations, but never names that sibling to make the distinction explicit.

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?

'Optionally limited to one entity' indicates one usage mode, so an agent can infer scoping behavior. However, there is no explicit guidance on when to reach for this versus find_relations or evidence_between, and no stated preconditions.

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