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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context beyond the annotations: OFAC SDN screening lists, Ethereum and Base chain coverage, risk score range, and activity metrics. No contradiction is present.

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 is a single dense sentence with a front-loaded purpose and a colon-separated list of outputs, containing no filler. It loses a point because the sentence is run-on and appears truncated at 'contract-vs-EOA dete', which slightly harms structural completeness.

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?

The description covers input type, output risk score, sanctions lists, chains, and activity metrics. An output schema exists for return values, and annotations already convey safety and idempotency. Missing explicit sibling alternatives and exact input JSON structure are minor given the overall clarity.

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?

The schema's only parameter 'input' has a generic Spanish description ('parametros del producto'), which is unhelpful. The tool description compensates by clarifying that the input should be an EVM wallet as a 0x address or ENS name, adding essential meaning the schema alone does not convey.

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 tool as wallet enrichment for EVM wallets via 0x address or ENS name, and lists concrete outputs: risk score, sanctions screening, and on-chain activity. It is specific enough to understand the tool's function, though it does not explicitly differentiate it from sibling tools like sanctions_screen.

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 implies usage through its outputs: if an agent needs wallet risk, sanctions exposure, or on-chain activity data, this tool is relevant. However, it provides no explicit when-to-use vs alternatives guidance and names no sibling tools or exclusion conditions.

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