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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description still adds real context beyond them: the reputation is "black-box" (computed/opaque rather than raw data) and it discloses the categories surfaced (tiers, gates, track record, evidence), which shapes what the agent should expect to reason over.

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; the return categories come immediately after the verb and the identifier constraint follows. Minor density cost from the parenthetical list and the near-synonym pairing of "black-box" and "opaque," but nothing is wasteful.

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?

One parameter, full schema coverage, an output schema, and rich annotations mean little else is required. The description supplies purpose, identifier constraint, and expected data categories — enough for correct invocation; only sibling disambiguation is absent.

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?

With a single parameter and 100% schema coverage the baseline is 3, and the schema only says "Opaque reputation subject id." The description adds a genuine constraint beyond that — the id is never a wallet address — which prevents a common mis-invocation.

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?

Specific verb ("Read") plus resource ("black-box public reputation") with the returned dimensions enumerated (tiers, gates, track record, evidence). It does not explicitly name the nearest siblings (get_agent_reputation, get_counterparty_reputation, get_my_reputation), so the agent must infer the boundary, but the "subject id, never wallet" framing does implicitly separate it from wallet-addressed lookups.

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: call this when you hold an opaque subject id. The clause "verified humans are addressed by subject id, never by wallet" functions as a partial when-not rule for the identifier, but no alternative tool is named and no prerequisites or exclusions are stated.

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