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

With no annotations, the description carries the full behavioral burden and does well: it discloses the $0.01 USDC x402 cost, indicates the output is factual rather than advisory, and implies a read-only snapshot. It does not explicitly state read-only status or rate-limit behavior, but the paid-read nature is clear.

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 first sentence front-loads the core purpose and return contents; the two short follow-up sentences add useful caveats about opinion-free output and cost. The long enumerated sentence is dense but each listed field helps an agent understand what the snapshot provides.

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?

Because there is no output schema, the description must explain return values, and it comprehensively lists risk score, token metadata, ownership/renouncement status, proxy detection, bytecode findings, and market data. For a one-parameter paid snapshot tool, an agent has enough context to invoke it correctly.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents that it expects a token contract address on OP Mainnet. The description reinforces the ERC-20/OP Mainnet scope but adds no meaningful syntax or constraint 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?

The description gives a specific verb/resource: a rug-check and due-diligence snapshot of an ERC-20 token on OP Mainnet. It lists the exact dimensions returned, making it clearly distinct from generic siblings such as optimism_contract_info or wallet-oriented 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?

The use case is implied by 'Rug check and due-diligence snapshot,' and the description clarifies that it returns facts only, with no buy/sell opinion. However, it does not explicitly say when to use this instead of related siblings like token_risk_check or optimism_contract_info.

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