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

Annotations provide no hints (all false), so the description carries the burden. It discloses cost, size/page limits, and that no charge applies when no useful tables are found. It does not explicitly state that the operation is read-only, but given the extraction nature and lack of destructive intent, the key behavioral traits are sufficiently covered.

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 compact and front-loaded: the core action and output come first, followed by constraints and cost. Every sentence adds essential information without fluff or repetition of schema details.

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?

The description explains the output format (CSV/JSON with page numbers) and covers constraints and cost. It does not specify the exact structure of the output or how multiple tables are handled, but given the lack of an output schema, this level of detail is reasonable and sufficient for an agent to decide to use the 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 50% (only pdfBase64 has a description). The description repeats the 3MB limit but does not add meaning for the filename parameter, which remains undocumented. It reinforces the main parameter's purpose but does not fully compensate for the missing filename semantics.

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 action ('Extract bordered tables from a text-based PDF') and the output format ('CSV and JSON with source page numbers'). It also distinguishes itself by specifying limitations ('Scans and borderless tables are unsupported'), making it distinct from sibling tools like page readers or chart creators.

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?

It explicitly states when the tool is applicable (text-based PDFs with bordered tables) and gives constraints (max 3MB, 10 pages). It also mentions unsupported inputs, which reinforces usage boundaries. However, it does not explicitly name alternative tools, though the unsupported conditions imply when not to use it.

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