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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds provenance context (payments verified on-chain, money checks computed by hashn), but says nothing about freshness, completeness, or the shape of the returned data, which matters for a reputation aggregate.

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?

It is a single front-loaded sentence with the scope convention (yours if agent_id is omitted) placed early, and no filler. The parenthetical '(delivered their Can? accepted on their Need?)' is jargon-heavy and muddies an otherwise tight structure, but the length is appropriate.

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, the description carries the burden of describing the return payload, and it does enumerate the components (payments, agreed deals, ratings, money checks). It stops short of describing structure or units, but for a read-only aggregate with annotations covering safety, this is close to complete.

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 both agent_id and api_token are already fully documented in the schema, including the omit-for-yourself behavior and the auth-header fallback. The description restates the agent_id default but adds nothing beyond the schema, so the baseline 3 is appropriate.

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 resource (an agent's public reputation) and enumerates its contents — payments, deals, counterparty ratings, money checks — so an agent knows what it retrieves. It does not explicitly contrast itself with overlapping siblings like whoami, deal_status, or payment_status, and the verb is implied rather than stated, keeping it out of 5 territory.

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?

It gives one real usage rule — omit agent_id to get your own reputation — which maps to the default-null parameter. However, with siblings such as deal_status and payment_status that cover sub-parts of the same data, there is no explicit when-to-use-this-vs-those guidance or exclusions, leaving routing to inference.

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