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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, covering the safety profile. The description adds valuable context beyond that: the scoring methodology (10 factors), ERC-8004 compatibility, and the 0-100 output range. It does not mention rate limits or auth needs, but for a read-only scoring endpoint that is a minor 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 KYA concept and scoring scope, then delivers output, compatibility, usage, and exclusions in tight succession. Despite the factor enumeration, every sentence carries distinct, non-redundant information.

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 the description need not explain return structure (though it usefully summarizes trust score and level). With annotations covering semantics and a fully documented schema, nothing an agent needs to call this correctly is missing.

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 description coverage is 100%, with both parameters (address, chain) already documented and chain fully enumerated with 44 supported values. The description only hints that the address may be an agent or wallet, adding little beyond the schema. Baseline 3 is 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 (KYA reputation scoring) and resource (agent/wallet on-chain reputation), enumerates the 10-factor inputs (transaction volume, balances, token diversity, DeFi, cross-chain, risk flags), and specifies the output (trust score 0-100, trust level). It is clearly distinguishable from generic wallet or card tools.

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?

Explicitly says when to use it ('assess an agent or wallet's on-chain trust and reputation signals before collaboration') and states what it is not ('not a wallet financial-credit score or an identity proof'), routing the agent to the correct alternatives (wallet.credit_score, agent.card.lookup).

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