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

With no annotations, the description carries the full burden and does disclose useful behavior: the underlying data source (GoPlus address security flags) and the exact checks returned (sanctioned, phishing, money laundering, mixer usage, honeypot exposure). It omits error/coverage behavior (chains, missing-data handling), and the trailing 'rolled From $0.010 USDC' appears truncated.

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 purpose in one sentence, which is good, but the ending 'rolled From $0.010 USDC' is a broken fragment that reads as truncated rather than deliberate pricing disclosure.

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?

For a single-parameter read tool with no output schema the description is adequate in coverage of what is checked, but it omits return shape, chain scope, and error behavior, and the garbled tail undermines confidence.

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?

One required parameter with 0% schema description coverage, so the description must compensate; it only implies the input is an EVM address with no format, chain, or checksum guidance. Adds minimal meaning beyond the schema.

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: a 'security/risk report for an EVM address' delivering a 'security score'. The '(EVM)' qualifier plus 'for an EVM address' distinguishes it from siblings like solana_risk_check and token_risk_evm (which covers tokens, not addresses).

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?

No guidance on when to use this vs the many adjacent risk tools (risk_check, trust_check, token_risk_evm, solana_risk_check). Usage is only implied by the scoping to EVM addresses.

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