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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description earns credit by going well beyond that: it defines the three evidenceLevel states and enumerates the flag semantics (attestation_rejected, in_dispute, revoked, concentrated_counterparty, etc.), which is meaningful behavioral context. It omits however anything about auth, rate limits, or failure behavior.

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 establishes the operation before the dense return-value enumeration. The output detail is lengthy but justified given there is no output schema; little is redundant.

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 full burden of explaining return values and does so thoroughly (score fields, evidence levels, flag vocabulary). For a simple one-parameter read it is essentially complete; only usage guidance 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?

Single parameter at 100% schema coverage, so the schema already documents agentId with its did:key format. The description's 'by did:key id' phrasing restates rather than extends that; 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 ('looks up') and resource ('an agent's INAM reputation') plus the keying parameter ('by did:key id'), so the operation is unambiguous. It does not, however, distinguish itself from nearby siblings such as inam_check or inam_search_agents, 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?

The description never says when to reach for this tool versus alternatives (e.g., inam_check or inam_search_agents), nor does it state prerequisites or exclusions. All of the text is about output semantics, leaving usage entirely to inference.

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