pdf_to_csv

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. However, it only says 'Convert PDF and scanned images into CSV representation' and does not explain how the conversion works, whether it is asynchronous, any performance implications, or output handling. The brief reference link is not a substitute for in-description transparency.

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 concise and front-loaded, stating the core purpose in one sentence and including a reference link. It avoids fluff but could be more structured with additional details. Still, it is appropriately sized for conveying the basic function.

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 the tool's complexity (11 parameters, no output schema, sibling tools like wait_job_completion and get_job_check suggesting an asynchronous job model), the description is incomplete. It fails to mention job-based behavior, return values, or any needed follow-up steps, leaving the agent without sufficient context to use the tool correctly.

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 input schema has 100% parameter description coverage, with detailed explanations for each of the 11 parameters (e.g., pages, rect, unwrap, line_grouping). The tool description itself adds no parameter-specific info, but the schema already does the heavy lifting, so a baseline score of 3 is appropriate.

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 converts PDF and scanned images into CSV representation with layout, columns, rows, and tables. It specifies the verb 'convert', the resource (PDF/scanned images), and the output format (CSV), distinguishing it from sibling tools like pdf_to_json and pdf_to_text.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention any preconditions, exclusions, or alternative tools for other output formats. The only clue is the tool name and CSV output implication, but this is not clearly stated as usage guidance.

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