extract_pdf_tables

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

Annotations already cover read-only/idempotent/non-destructive safety, so the burden is lower. The description adds genuinely useful behavior: the 100-page-per-call limit and the structured return shape (page number, dimensions, content). This goes beyond what annotations provide without contradicting them.

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?

Three sentences with no filler: the primary action is front-loaded, output details follow, then use-case guidance and a key limit. Every sentence adds information needed for correct tool selection and invocation.

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 absence of an output schema, the description competently explains what is returned and the scan limit. It does not explicitly state that either url or file_base64 is required, but the schema descriptions cover that. Overall it is sufficient for correct use without being exhaustive.

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 100%, so the schema already documents all 7 parameters well. The description mentions Markdown/CSV/JSON and table content, but does not add parameter-specific semantics beyond what the input schema already states. Baseline 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 opens with a specific verb and resource ('Extract data tables from a PDF') and clearly defines the delivered artifacts (page number, dimensions, content in Markdown/CSV/JSON). It also differentiates from sibling conversion tools by emphasizing tables over prose, so an agent can distinguish it from convert_pdf_to_markdown or read_pdf_pages.

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 gives clear context for when to use the tool: 'Ideal for financial statements, spec sheets, price lists and any document where tables matter more than prose.' It implies when the tool is appropriate, though it does not explicitly name alternatives or state when not to use it, so it stops 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.