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

Annotations only say it is not read-only and not destructive; the description adds substantial behavioral context beyond that: it returns 202, a human fetches and checks the evidence, and the caller is emailed either way — making the async human-in-the-loop nature explicit. It also discloses auth expectations (no ownership proof) and pricing/billing behavior. No contradiction with annotations.

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 dense but efficient, front-loading the core action ('Send the claim in words and a URL') before pricing and alternatives. Every sentence carries information. The stylistic 'INFLUENCE —' opener and quoted framing are slightly oblique but don't waste words; the apis://prices pointer is a reasonable way to defer pricing 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?

With no output schema and sparse parameter descriptions, the description carries a heavy burden. It covers the overall flow well (submit → 202 → human review → email either way) and pricing, but leaves 'slug' undefined (what does it identify — the finding? the listing?), which an agent needs to invoke correctly. The evidence_url requirements are also 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 coverage is only 20% (only 'context' has a description), so the description must compensate. It maps 'claim' to the claim-in-words and 'evidence_url' to the evidencing URL, and 'emails you either way' implies the role of 'contact.' However, the required 'slug' parameter is completely unexplained in both schema and description, and 'contact' format is not specified — a real gap for a required param.

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 concrete action — send a claim in words plus an evidence URL to dispute a finding — and the title adds 'Dispute a finding on a listing you own.' It names the sibling it is not (report_correction), which helps disambiguation. Minor deductions: 'finding' assumes internal vocabulary, and the title's ownership framing slightly conflicts with the description's explicit statement that ownership proof is not required.

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 gives explicit when/when-not guidance: any paying caller can use this to dispute data, and if it's your own company, report_correction is free instead. It also states eligibility ('open to any paying caller... should not have to prove ownership') and pricing conditions (included in Influence vs. $49 one-off, never from prepaid balance). This fully routes an agent to the right tool.

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