pdf_to_json

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

With no annotations, the description carries the full transparency burden. It discloses that the output is a JSON file containing pages, text, and metadata, which is useful. However, it does not mention side effects like file overwriting, directory creation, or how the tool handles scanned/non-text PDFs.

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?

A single, front-loaded sentence delivers the essential information without any filler. Every component (PDF, pages/text/metadata, JSON file) is meaningful and no examples or redundant phrasing are included.

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 simple conversion tool with only two parameters, the description conveys the core behavior sufficiently. However, because there is no output schema or annotations, a bit more context about the resulting JSON structure or limitations (e.g., scanned PDFs) would make it fully complete.

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 describes both parameters (file and output_name) with 100% coverage, so the baseline is 3. The description adds little beyond the schema, only implicitly tying 'file' to the input PDF and output_name to the JSON file.

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 exports PDF structure (pages, text, metadata) as a JSON file. The specific verb 'export' and the output format 'JSON file' make the purpose unmistakable and distinguish it from sibling PDF conversion tools.

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 when a JSON representation of PDF content is needed, but it does not explicitly say when to choose this over alternatives like pdf_to_markdown, get_page_text, or extract_tables. No exclusions or alternative guidance are provided.

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