read_paper_pdf

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

No annotations, so the description carries the burden and does reasonably well: it discloses the side effect of downloading a URL result to the server's pdf dir, the truncation behavior governed by max_chars, and the empty-text-plus-note outcome for scanned PDFs. It omits error behavior for invalid paths/URLs and any size or time limits, so it earns a 4 rather than a 5.

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, no filler, front-loaded with purpose then download behavior then return/edge-case behavior. Slightly dense in the middle sentence but every clause carries information.

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 3-parameter read tool with no output schema, the description covers the return shape (local_path, page_count, char count, text), the download side effect, truncation and the scanned-PDF case. Remaining gaps, such as error handling and max_chars units, are minor.

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% and the description supplies meaningful semantics for two of three parameters: path_or_url (local path or http(s) URL) and page (one page instead of the whole document), while max_chars is only implied by the word 'truncated'. This compensates for the schema gap without fully documenting every parameter's default and units.

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?

States a specific verb (extract) and resource (full text of a PDF) with accepted input forms (local path or http(s) URL). Clearly distinguishable from siblings, which are all search/extraction tools for other sources; none of them read a local PDF.

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?

Usage is implied by the input types (use a local path or URL), and the OCR note hints at a fallback path, but it never says when to prefer this over extract_url for a remote PDF or what to do instead for a scanned document beyond 'run through OCR'. No exclusions or named alternatives.

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