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

No annotations, so the description carries the full burden. It discloses what is checked (scams, address mistakes, risk signals) but not whether any state is mutated, what happens to the address, whether it requires auth, or how results are returned. For a risk-check tool this is thin.

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?

Single tight sentence with no waste. Front-loaded with the verb and resource. Adequately sized for what it covers, though it could do more.

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?

No annotations, no output schema, 0% schema coverage, and no parameter explanations. The description is too sparse for a multi-parameter risk-assessment tool; an agent cannot confidently know how to fill chain or amount, or what the response looks like.

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 0%, so the description must compensate but provides no parameter meaning. It implies an address is checked but doesn't explain 'chain' (default EVM) or what 'amount' is used for, leaving two of three parameters undocumented.

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?

Clear verb 'check' and resource 'crypto transaction', with scope spelled out (scams, address mistakes, risk signals). Distinguishes from sibling check_transactions_batch by implication (singular, one transaction), but doesn't name it 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?

No guidance on when to use this vs preflight_transaction, check_transactions_batch, or report_scam_address. The word 'check' suggests a read-only inspection, but the agent must infer this; no when/when-not or alternatives are given.

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