batch_parse_pdfs

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

With no annotations provided, the description carries the behavioral disclosure burden. It transparently lists all output artifacts (pages.json, summary.txt, PNGs) and states that a JSON summary is returned. It does not mention potential overwrite behavior or whether the output folder is created automatically, but the write side effects are clearly disclosed.

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 tightly structured with a clear lead sentence followed by a bullet-style list of output files. There is no redundant prose, and every sentence contributes functional information. This is an example of efficient, well-organized documentation.

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 batch processing tool with four parameters and an output schema, the description covers the main inputs and outputs effectively. It lacks some edge-case details like non-recursive folder scanning or failure handling for individual PDFs, but the 'successes and any errors' summary and parameter schema fill most gaps. A 5 would require explicit statements about overwrite behavior or scope limitations.

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 already covers all four parameters at 100% description coverage, providing a baseline of 3. The tool description adds value by concretely demonstrating how output_folder is used in the file path '<output_folder>/<stem>/' and what files result, going beyond the schema's short 'Where to write outputs' description.

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's function: 'Parse all PDFs in a folder' and enumerates the exact output files. It distinguishes itself from sibling tools (parse_pdf, screenshot_pdf, cited_screenshot) by focusing on batch folder processing rather than single-document or individual screenshot operations.

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 phrase 'all PDFs in a folder' clearly implies this tool is for batch scenarios, contrasting with the singular parse_pdf sibling. However, it does not explicitly state alternatives or when not to use this tool (e.g., if only one PDF needs processing), so it falls short of a 5.

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