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

Annotations declare readOnlyHint and openWorldHint, but the description adds genuinely new context: latency ('Seconds'), that the call is paid (0.55 USDC via x402 at a specific endpoint), and that a 10% fee is set aside. Payment and per-call cost requirements are exactly the kind of behavioral detail annotations cannot convey. The verification/agent-identity block is largely promotional rather than operationally useful.

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 is well front-loaded with the actual capability and the second gives the input shape. But roughly half the text is boilerplate about ERC-8004/Virtuals identity, payout wallet addresses, and the GHOST77 token, which is marketing filler rather than invocation guidance. The payment line is justified; the identity/verification block is not.

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 must convey what comes back, and it does — verdict and risk level plus enumerated flags. Combined with an explicit input example and 100% schema coverage, an agent has enough to call it correctly; only the return payload's shape remains slightly underspecified.

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 100% and the network enum is present, so the schema already fully documents both parameters. The description's inline example ({"network":"base","contract_address":"0x..."}) adds a small concrete usage illustration but no semantics beyond the schema. Baseline 3 is appropriate.

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?

Opens with a specific verb+resource framing ('Spot dangerous admin powers') and enumerates the concrete checks: verified-source status, proxy/implementation/admin, owner type, privileged functions, token risk flags, verdict and risk level. An agent can tell this is a contract-level security scan rather than a token DD or honeypot check, though it never names those siblings 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?

The phrase 'Automated read-only scan, not a full audit' sets a useful scope boundary and implies when this is appropriate (quick safety check, not deep due diligence). However, it never routes the agent away from near-neighbors like rug_honeypot_quick_check, contract_research, or token_due_diligence, so the choice between them is left to inference.

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