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

Annotations already declare the safety profile (readOnly=false, openWorld=true, idempotent=false, destructive=false), so the bar is lower. The description adds genuinely new behavioral context: a $0.20-per-successful-call prepaid cost and the fact that the value is computed via an unsigned simulated sweep rather than a direct read. It does not, however, reconcile the 'simulated/unsigned' language with the readOnlyHint=false annotation, and it omits auth and rate-limit details.

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?

Two tightly packed sentences with no filler; the cost is front-loaded before the value proposition. It is efficient, though the extreme terseness trades away clarity that this cryptic domain actually needs.

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?

For a paid, open-world web3 tool with a nested request object and no output schema, the description is too thin. It never defines what a 'collectible amount' is, how curve vs. escrow scoping behaves, or what the response contains, so an agent cannot fully predict the call or its result.

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 0%, so the description carries the burden. It mentions 'curve/escrow' and thereby hints at the optional curve field, but the required chain, wallet, and platform fields go entirely unexplained in both the schema and the description. This leaves the majority of the request contract 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?

The description says it returns "TRUE collectible amount per curve/escrow via unsigned simulated sweep," which points to a quote/compute resource tied to curve/escrow. However, "collectible amount" and "curve/escrow" are jargon that leaves the exact deliverable ambiguous, and it doesn't distinguish itself from sibling tools like claim_worth_it or launch_economics. Purpose is inferable but not crisp.

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 only usage signal is the contrast "raw RPC overstates reality," implying this is preferred over reading raw RPC. There is no when-to-use guidance relative to the nine sibling tools, no stated prerequisites, and no exclusions. Anything beyond that single hint must be inferred.

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