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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, but the description adds real context the annotations can't: no auth required, default reply shape, and an explicit honesty caveat that the Base-mainnet USDC escrow is runtime-gated, restricted to buyer/seller/fee destination, and not third-party audited. That risk disclosure is exactly the kind of value-add this dimension rewards.

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 onboarding priority in the first sentence, then supporting detail. The trailing ⚠️ rails block is dense but is genuine disclosure rather than filler; slightly heavy for an 'info' tool.

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 output schema exists, and the description compensates by enumerating what the compact reply contains (overview, network/payment-rail honesty, live stats, quick start) and what the full form adds. Enough for an agent to know what it will receive in either mode.

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 optional boolean with 100% schema description coverage, so the schema already does the work and baseline 3 applies. The description reinforces it by noting full=true returns the same long-form content as the webaz://guide/info resource, a marginal but useful addition.

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 and resource ("Get WebAZ overview + live network_state") plus the onboarding entry-point role. It doesn't name overlapping siblings like webaz_get_status or webaz_connection_status, but "Call FIRST when onboarding" still gives the agent a clear ordering signal.

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?

Explicitly says when to invoke ("Call FIRST when onboarding") and names an alternative route for deeper content (MCP resource webaz://guide/info or {"full":true}). No explicit when-not-to-use or sibling exclusion, so it falls short of a 5.

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