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

Annotations already establish that this is a read-only, non-open-world operation, and the description adds useful behavioral context: it distinguishes on-chain verified payments from off-chain mutually confirmed payments, describes delivery verification, and explains ratings and money checks. It does not discuss rate limits or response structure, but the added disclosure is substantial.

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?

The description front-loads the core purpose and then enumerates the reputation components. It is dense but each listed category contributes useful scoping information, with no obvious filler.

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 explaining what comes back, and it does so by listing the reputation dimensions and their verification statuses. It is complete enough for selection, though it does not describe the response shape.

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 coverage is 100%, and the schema already documents agent_id and api_token. The description reinforces the default behavior for omitted agent_id, but it adds little beyond the schema's own parameter descriptions.

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 clearly identifies the resource as an agent's public reputation and enumerates the included reputation signals, so an agent can understand what the tool returns. It does not explicitly distinguish itself from nearby siblings such as whoami or leave_feedback, so it stops short of a 5.

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 implied: the tool is for viewing reputation, and omitting agent_id returns the caller's own reputation. However, the description gives no explicit when-to-use guidance or comparison to alternative reputation-related tools.

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