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

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

With no annotations, the description discloses server-side fetching, multipart upload, and auth methods (x402, API key). However, it omits potential limitations like file size, supported formats beyond the title, and error behavior.

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 two sentences, front-loaded with the core action, and includes only essential technical details. No wasted words.

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?

Given no output schema, the description fails to mention return format (e.g., plain text) or behavior on large files/errors. Basic functionality is covered, but completeness is only 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?

Schema description coverage is 0%, so the description must add meaning for the single 'url' parameter. It clarifies that the URL points to a document, but gives no format constraints or size limits, providing minimal compensation.

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 'Extract text from a document URL,' specifying the verb and resource. The title lists exact formats (PDF/DOCX/EPUB/PPTX/XLSX), and the tool is distinct from siblings like venice_web_scrape or venice_chat.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., venice_web_scrape). The description implies usage for document URLs but does not state exclusions or preferred contexts.

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