extract_pdf

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two meaningful traits — that it performs a network download and that it returns both text and metadata — but says nothing about truncation for long documents, failure behavior on non-PDF or paywalled URLs, authentication needs, or page limits.

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?

One sentence, front-loaded with the action and resource, with no filler. It could afford one more clause about page limits without becoming bloated, but nothing present needs to be cut.

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?

An output schema exists, so return-value detail is not required. Still, for a two-parameter fetch-and-parse tool with zero annotation coverage, the description leaves out page-limit semantics and error conditions, which are exactly the things an agent would need to call it predictably.

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 ideally should compensate, and it partially does by making clear that 'url' is a remote PDF location and that text plus metadata are returned. However, the 'max_pages' parameter (default 20) is never mentioned, so an agent gets no explanation of truncation behavior or what happens to content past the default limit.

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 gives a specific verb pair (download and extract) and a specific resource (full text and metadata from an online PDF), which lets an agent distinguish it from siblings like extract_docx_document or extract_xlsx_spreadsheet without opening the schema. It stops short of explicitly naming those siblings as alternatives.

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 word 'online' implies this tool takes a remote URL rather than a local file, which is a useful if implicit scoping cue. Beyond that there is no guidance on when to choose this over scrape_url, search_and_scrape, or the other extract_* tools, and no mention of prerequisites such as the URL needing to point directly at a PDF.

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