pdf_extract_tables

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

No annotations are provided, so the description carries full burden. It mentions 'structures resembling data tables', hinting at imperfect extraction, and 'text stream', implying reliance on text layer. However, it omits critical details: no mention of read-only nature, required permissions, file size limits, or behavior with scanned PDFs. For a tool with no annotations, this is insufficient.

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 a single sentence of 12 words, highly concise. It front-loads the main action. However, a more structured format (e.g., separating input/output details) could improve readability, but it is not verbose.

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 only hints at output format (Markdown). It lacks details on expected output structure, error handling, or edge cases. For a tool with two parameters and no annotations, the description is adequate but could be more 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 has 2 parameters with 100% description coverage. The description adds no additional context beyond the schema. According to guidelines, baseline is 3 when coverage is high, and the description does not supplement or clarify parameter usage.

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 table-like structures from PDFs and outputs Markdown. The verb 'extract', resource 'tables', and output format are explicit. It distinguishes from sibling tools like pdf_convert_to_markdown which converts entire document, and pdf_convert_to_text which extracts plain 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 implies usage for table extraction but does not explicitly state when to use this tool versus alternatives like pdf_convert_to_markdown or pdf_convert_to_text. No when-to-use, when-not-to-use, or prerequisite information is provided.

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