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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that by naming the data sources (published scorecard and feed reconciliation record) and the shape of the returned evidence (sample sizes, confidence bounds, links), telling the agent this is a verified, publication-grade artifact rather than a raw feed read. It does not state freshness/as-of semantics, which would be the remaining gap.

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 with no filler: verb first, then the returned fields, then the provenance. Every clause carries information and nothing is restated from the title.

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 input schema and no output schema, the description carries the burden of describing the return payload, and it does so by enumerating sample sizes, confidence bounds and evidence links plus their source records. Complete enough to call correctly; only the currency/recency of the published scorecard is left unaddressed.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly avoids inventing arguments and instead spends its words on what the parameterless call yields.

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+resource ('Returns the public proof summary') and enumerates the contents: sample sizes, confidence bounds, evidence links. The word 'public' plus the named source records (published scorecard, feed reconciliation) differentiate it somewhat from internal siblings, but it never explains how it differs from get_accuracy_proof or get_proof_anchors, which sound like adjacent proof artifacts.

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 when-to-use guidance and no exclusion of alternatives, despite at least three siblings with overlapping proof/trust semantics (get_accuracy_proof, get_proof_anchors, get_feed_trust_summary). The agent must infer from the name alone that this is the aggregate public-facing summary rather than the per-proof detail.

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