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

With no annotations, the description carries the full burden and largely meets it by explaining the semantics of the returned fields: 'countersigned' vs 'independently_verified', the meaning of components.attestedReceipts > 0, and that an 'attestation_rejected' flag is a strong negative. It does not cover error behavior for an unknown agentId or any auth/rate-limit context, leaving a modest gap.

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?

Front-loads the purpose and returned fields, then layers in interpretation warnings in a compact set of sentences. Dense but each sentence contributes; the field-semantics clauses are slightly run-on but not 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?

There is no output schema, so the description must convey what is returned and how to read it — and it does, naming the reputation components, the evidenceLevel distinctions, and the negative attestation flag. An agent has enough to invoke the tool and act on the result.

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% for the single parameter and the schema already documents it as a 'did:key:... id'. The description's 'Takes a did:key agent id' merely restates that, adding no format, validation, or resolution detail beyond the schema.

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 (look up) and resource (an agent's INAM reputation) and enumerates what comes back: trust score, finalized-receipt count, success rate, dispute flags. It is clearly distinguishable from siblings like inam_search_agents (discovery) and inam_get_receipt (single receipt).

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?

Gives clear context for when to call it ('before deciding whether to trust or transact with it') and adds decision guidance ('Do not decide on trustScore alone: check evidenceLevel first'). It does not name a sibling alternative or state an exclusion condition, so it falls short of a 5.

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