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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds the useful 'black-box' framing, implying the response is an aggregated verdict rather than raw underlying data, but it does not say what happens for an unknown or unregistered agent id, which is the main failure mode for an openWorld read.

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 the resource and scope before the mechanism, and no filler. 'Black-box' is slightly jargon-laden but carries real meaning about the return shape, so almost nothing is wasted.

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 one-parameter read with an output schema and full annotation coverage, the description supplies enough: what it returns, whose reputation it is, and that it is public. The remaining gap is error behavior for unknown agent ids, which the output schema cannot express.

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?

Only one parameter and the schema already documents it at 100% coverage ('Registered agent id.'). The description restates that the lookup is keyed by agent id without adding format, source, or lookup semantics, so the baseline 3 applies.

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 (Read) and resource (public reputation) and enumerates the payload categories (tiers, gates, track record, evidence) scoped to a registered agent id. It implicitly separates itself from self-scoped siblings like problee_get_my_reputation via 'public' and 'by its agent id', but never names the sibling it differs from, so the distinction is inferential rather than stated.

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: 'public' and 'registered agent' hint that this is for looking up another agent rather than yourself, but there is no explicit when-to-use, no when-not-to-use, and no named alternative among the several reputation tools (get_my_reputation, get_counterparty_reputation, get_subject_reputation, get_trader_profile).

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