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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the trailing 'Read-only.' sentence merely repeats structured data and earns no credit. The description does add real behavioral content by disclosing what evidence each mode returns (tx evidence, evidence-root check), but omits failure behavior, whether on-chain lookups require network/RPC access, and what happens when no mode parameter is supplied despite zero required parameters.

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 compact, front-loaded clauses keyed by parameter name make it fast to scan, and nothing is padded. The final 'Read-only.' sentence is redundant with the annotation, and the fragmentary telegraphic style costs some 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?

An output schema exists, so return formats need not be spelled out, and the description correctly focuses on mode semantics. But for a four-parameter multi-mode tool with no required fields and one entirely undocumented parameter, the definition leaves open what an empty call does and how modes interact.

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 description must carry the parameter burden, and it does explain three of the four parameters with meaningful semantics beyond their types. However, 'expectedSigner' is never mentioned despite being a non-obvious parameter (an expected-address pin for signature checks), leaving a clear gap.

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 names the tool's three operating modes (document, evaluator, serviceId) and states concretely what each checks: signature and on-chain checks of a trust manifest/attestation/agent card, raw reputation counts with tx evidence, and delivery score with signature and evidence-root check. It is specific about resources and checks, though it never states a top-level verb like 'verify' in prose and leaves the mode-selection rule implicit rather than 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?

Usage is only implied: passing 'document' vs 'evaluator' vs 'serviceId' implicitly selects the mode, and the per-mode outputs hint at which to pick. There is no explicit when-to-use phrasing, no statement that only one mode should be supplied at a time, and no pointer to sibling tools (find_service, get_order) for the surrounding workflow.

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