extract_tables

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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds useful behavioral context such as the absolute-path requirement, the server page limit, and the output structure including header rows and spanning-cell behavior.

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 front-loaded with the tool's purpose and is organized into output-shape details followed by an Args section. It is somewhat longer than necessary given the output schema, but the extra detail about table structure and spanning cells earns its place.

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 two-parameter, read-only extraction tool with an output schema, the description covers the essential purpose, both parameters, page scoping, and non-obvious table semantics. It does not address edge cases such as scanned PDFs or encrypted files, but those are secondary for this tool.

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 0%, so the description must carry parameter meaning, and it does: `path` is defined as an absolute local path, and `pages` as 0-based pages to inspect with omission meaning the whole document. The only minor gap is that the actual server page limit is not stated.

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 that this tool returns tables from a local PDF as rows of cell text, which is specific enough to distinguish it from text or markdown extraction in practice. However, it does not explicitly name or contrast the sibling tools, so it falls short of the top score for sibling differentiation.

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 tool's usage is implied by its table-focused purpose, and the description explains that `pages` can be omitted to process the whole document. It does not explicitly say when to use this tool instead of `extract_text`, `extract_markdown`, or `extract_blocks`.

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