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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real value beyond the schema by disclosing the ERC-8004 output composition and the $0.025 cost, but says nothing about latency, data freshness, or what an unknown address returns.

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?

Three tight sentences, front-loaded with the core action and format, with the cost tacked on at the end. No filler, though the parenthetical schema enumeration is slightly dense.

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?

An output schema exists, so return values need not be explained, and the low parameter complexity is well handled. The main gap is the missing routing signal against the agent.reputation sibling, which an agent would need to pick correctly between the two.

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% with only 2 parameters (address required, chain enum with default), so the schema already documents everything. The description adds no parameter-level meaning, making the baseline 3 appropriate.

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 and resource ('Get agent reputation') plus the output format (ERC-8004 standard: Identity + Reputation + Validation Registry schema). The phrase 'same KYA analysis but formatted for on-chain registry compatibility' implicitly differentiates it from the agent.reputation sibling, though it never names that sibling explicitly.

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 format contrast ('same KYA analysis but formatted for on-chain registry compatibility') implies when to pick this over the plain reputation tool, but no alternative is named and there is no explicit when-to-use/when-not guidance. Usage is left to inference.

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