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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new epistemic context: assumptions are 'untrusted authored content rather than platform truth claims', which tells the agent how much to trust results. It does not add rate limits or return-format detail.

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?

Three tight sentences: use condition first, alternatives second, trust caveat last. No filler, though the opening sentence is somewhat long and the trust caveat might be better placed before the routing list since it qualifies the data being fetched.

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 read-only, non-destructive filter tool with full schema coverage, the description supplies use conditions, alternatives and a trust caveat. It could say more about what a result set looks like (no output schema exists), but nothing needed to invoke it correctly is missing.

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 all five params (trail, status, model_claim, cascade_potential, verification_cost) are already documented in the schema, including the caveat that model_claim is unverified. The description echoes the filter fields but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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?

Names the resource (participant-declared assumptions) and its distinctive fields (transparent status, cascade-potential, verification-cost), and distinguishes itself from commons_search, commons_disputes and commons_negative_results. However, it never uses an explicit verb like 'retrieve' or 'list', so the operation itself must be inferred from the name and the 'Use when' framing.

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?

Explicitly states the condition for use ('when you specifically need participant-declared assumptions and their transparent status, cascade-potential or verification-cost fields') and routes three alternatives to their own scenarios (general text, contested targets, outcomes/retired paths). Nothing is left to inference.

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