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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds substantial context beyond them: this is a paid x402 call with two price tiers, how to pass payment, that verdicts arrive with cited reasons and a list of checks that could not run (partial-result disclosure), and who operates it. That is material behavioral information the schema cannot convey.

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-loaded with the purpose and verdict categories, then the check list, then the pricing/depth detail and payment instruction. Dense but nearly every sentence carries new information; the check enumeration is long but useful for judging coverage.

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 carries the return-value burden and does so reasonably: verdict categories, cited reasons, and the 'checks that could not run' field. It does not describe the structure of the cited-reasons payload or response size, but an agent has enough 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?

Schema coverage is 75%, and the description still adds meaning: it explains the quick versus deep depth split ('deep adds full hook inspection, IMD admission checks and a written explanation'), the $0.25 pricing, and instructs passing the x402 payload as `payment`. holderWallet is left entirely to the schema, which is acceptable given its long inline description.

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 ('token safety and security verification', 'pre-buy verdict on an Ethereum token') and enumerates the exact checks and possible verdicts. An agent can tell it apart from token_price, wallet_check, or hook_inspect without inspecting either schema.

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 clear context ('when an agent needs a pre-buy verdict') and a concrete depth tradeoff (deep adds hook inspection, IMD admission checks, written explanation). It does not name alternatives or exclusions, even though siblings like hook_inspect, watchtower_check, and verdict_preview overlap in purpose.

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