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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one genuinely useful trait — the figures come from 'recorded reconciliation checks' rather than live data — but it never explains what a 'verdict' value can be, how stale the checks are, or whether coverage is a percentage or a count.

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?

One front-loaded sentence with zero filler; the subject ('per venue verdicts, coverage and sample counts') arrives immediately. Slightly noun-dense phrasing ('from its recorded reconciliation checks') costs a little readability but conveys real information.

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 single optional-parameter read tool with no output schema, the description does list the returned components, which is the right move. However, without an output schema it should also pin down the shape and meaning of 'verdict' and 'coverage', and it leaves the reader unable to distinguish this tool from get_feed_trust_summary.

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 100% with the single optional venue parameter fully described, including example values. The description only echoes the per-venue grouping, adding no syntax or filtering semantics beyond the schema. Baseline 3 applies since the schema does all the work.

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 concrete verb ('Returns') and enumerates the payload: per-venue verdicts, coverage and sample counts for the liquidation feed. That is far more specific than a name restatement. It stops short of differentiating itself from the near-identically named sibling get_feed_trust_summary, so an agent must guess at the summary-vs-detail split.

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 is purely declarative ('returns X') and gives no when-to-use condition, no when-not-to-use, and never mentions the obvious alternative get_feed_trust_summary or get_liquidation_census. The only usage cue is the schema note 'Omit for all', which is parameter-level, not tool-selection guidance.

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