textokit_web_read

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the cost model (0.001 USDC per call via x402 on Base from a wallet) and the free-sample alternative, but it omits details such as payment flow, rate limits, error behavior, and output truncation beyond what the schema covers.

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?

The description is three short sentences with no wasted language. It front-loads the core purpose, then payment terms, then the free-sample pointer.

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?

The tool is moderately simple, but with no annotations and no output schema, the description should do more to set expectations about returns and payment prerequisites. It adequately covers purpose, cost, and public-URL scope, but leaves payment-flow and output-shape details implicit.

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 the schema already documents url, format, and maxChars in detail. The description adds no parameter-specific meaning beyond the schema, which is the expected baseline when schema coverage is complete.

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 gives a specific verb and resource: 'read any public URL as clean text' and 'Web page to Markdown.' It is clear what the tool does, but it does not explicitly distinguish this tool from sibling textokit_url_text, so it falls short of a 5.

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 description implies usage by saying it reads any public URL and points to textokit_sample for a free sample. However, it does not explain when to choose this paid tool over similar siblings such as textokit_url_text, nor does it state exclusions beyond public URLs.

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