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

Annotations already declare non-readonly, non-destructive, non-idempotent, closed-world, so the safety profile is covered. The description adds genuine context beyond that: cost of 25 USDC on Base, zero model calls, hard input bounds, return artifacts, and the payment/wallet authorization prerequisite. It does not say what happens on partial failure of the audit vs. quarantine, but the disclosure is strong.

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?

Three dense sentences with the cost and payment model front-loaded, then semantics, then constraints. Nearly every clause carries information. Slight congestion from packing pricing, limits, and payment protocol into one paragraph.

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 naming the three return artifacts (cleaned CSV, quarantined exceptions, audit). Combined with cost, bounds, and the x402 dance, an agent has what it needs to invoke correctly; only the undocumented optional parameters (required, unique_key) leave a gap.

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 only 17%, so the description must compensate. It adds useful constraints (64 KiB CSV, max 20 columns, 500 rows) and implies the trim and duplicate-removal behaviors, but never explains the `required` array, the `unique_key` nullable parameter, or the exact semantics of `mapping` beyond 'map columns'. Partial compensation, not full.

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 specific verbs and resource: map columns, trim fields, remove exact duplicate output rows, returning cleaned CSV plus quarantined exceptions and an audit. It also bounds the operation (500 rows, 20 columns, 64 KiB) and explicitly excludes fuzzy matching/enrichment, which no sibling does, so it is unambiguous against website_html_check.

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 a clear procedural path: call without payment to obtain x402 requirements, then retry with the signed PaymentPayload in params._meta["x402/payment"]. It also names the exclusion (no fuzzy matching or enrichment) so the agent knows when this is the wrong tool. Lacking only a direct statement of alternatives/limits on retry behavior.

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