Venice Text Parser (PDF/DOCX/EPUB/PPTX/XLSX)

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

No annotations are provided, so the description carries the full burden. It discloses key behaviors: server-side URL fetching, multipart/form-data upload, and supported formats — all genuine additions. However, it doesn't disclose output format details (does it return plain text? structured JSON?), limits, or failure behavior for unsupported formats, which would be valuable for a parsing tool with no output schema.

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 compact at about three sentences and leads with the core purpose. Every sentence contributes: extraction purpose, file formats, auth methods, and operator preference. The format-details line could arguably be trimmed, but it's informative. Slightly dense but well-organized and front-loaded.

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 single-parameter tool with no output schema and moderate complexity, the description covers the essential input behavior well. However, missing output format expectations and error/failure behaviors for a parsing tool is notable. Given the auth complexity (x402 vs API key) and document parsing nature, a bit more detail on return structure and constraints would improve completeness, but the description is largely adequate.

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?

The schema has a single 'url' parameter with 0% description coverage, so the description must compensate. The description does add meaning: it clarifies the URL is fetched server-side and the file is uploaded as multipart/form-data — context that isn't in the schema. However, it doesn't specify URL format requirements beyond the schema's 'uri' format hint, omitting details like whether signed URLs or authorization headers are supported.

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 clearly states the tool extracts text from a document URL, explicitly lists supported formats (PDF/DOCX/EPUB/PPTX/XLSX), and includes a specific verb+resource ('Extract text from a document URL'). It distinguishes well from siblings like venice_web_scrape (generic web scraping) and venice_asr (audio transcription) by being explicitly document-focused.

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 states it fetches the URL server-side and specifies an operator preference parameter, providing some context for how it's invoked. However, it doesn't explicitly state when to use this tool versus alternatives (e.g., when one would choose this over venice_web_scrape for PDFs), nor does it provide exclusions or prerequisites. The auth note ('x402 wallet auth') adds useful access context.

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