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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile needs no restating. The description adds genuinely useful context beyond that: the shape of the response and the plan gate ('Builder plan and above'). It says nothing about behavior on unknown/non-EVM hashes, latency, or rate limits.

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 with no filler: purpose and return values first, then use cases, then the plan requirement. Front-loaded and every clause carries 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?

With no output schema, the description usefully enumerates the return payload and adds the access-tier constraint. The remaining gaps are the undocumented chain parameter and no guidance on failure cases for invalid or unknown hashes.

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 0%, so the description carries the full burden. It clarifies that 'hash' is an EVM transaction hash (a real semantic gain), but the 'chain' parameter and its 'eth' default are never mentioned, leaving an agent unaware that non-Ethereum chains can be targeted.

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+resource (analyze an EVM transaction by hash) and enumerates the returned fields (status, value, counterparties, risk flags for sanctions/exploit/phishing/scam). It is clearly distinct from entity/wallet screening siblings, though it never explicitly contrasts itself with screen_transfer, which handles a similar object.

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 three concrete usage contexts: post-trade monitoring, incident triage, and fraud investigation. No when-not-to-use conditions and no named alternative (e.g. screen_transfer for pre-signature checks) are provided, so the routing decision is only partly covered.

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