well-005-csv-to-table

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description still adds substantial non-obvious behavior: request caps, redirect limit, silent-truncation-with-warning at 5000 rows, a per-call x402 payment, and a 'nothing stored' data-retention statement. This is exactly the extra context an agent needs beyond the hints.

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 purpose, then constraints, then return shape, then the warranty/persistence note — each clause adds distinct operational value. Dense but zero filler sentences.

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?

Despite having no output schema, the description enumerates the exact return shape ({ url, final_url, content_type, headers, rows, row_count, warnings }), so the agent knows the response. Limits, payment, and retention are all disclosed; nothing needed for correct invocation is absent.

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%, so both parameters are already documented in the schema. The description restates 'Optional has_header (default true)' which duplicates rather than extends the schema text. Baseline 3 is correct when the schema carries the parameter burden.

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 opens with a precise verb+resource+output pair: 'Fetch a public https CSV URL and parse it into headers + rows'. An agent immediately knows exactly what the tool produces, and the added cost note ($0.005 USDC via x402) further distinguishes it. No siblings exist, so no differentiation is needed.

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?

It clearly states the applicability boundary — 'https only' with http, file, data, localhost, and private IPs rejected — plus concrete limits (1 MB, ~10s, 5 redirects, 5000 rows). What's missing is any explicit when-to-use-vs-alternative framing, but with no sibling tools there is nothing to route against, so 4 is appropriate.

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