pdf-reader

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

No annotations are provided, so the description carries the full burden. It mentions that the tool 'Returns the full text content and metadata,' which gives some behavioral insight into output. However, it lacks details on error handling (e.g., invalid paths, corrupted files), performance (e.g., large file handling), or side effects (e.g., file locking). For a tool with zero annotation coverage, this is a significant gap in behavioral disclosure.

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 two sentences, front-loaded with the core purpose and followed by return information. Every word earns its place with no redundancy or fluff, making it highly efficient and easy to parse.

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 tool's moderate complexity (reading PDFs) and lack of annotations or output schema, the description is adequate but incomplete. It covers the basic purpose and output types but misses details on parameter semantics, error conditions, and behavioral nuances. For a tool with no structured support, it provides a foundation but leaves gaps in full contextual understanding.

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?

The input schema has 1 parameter with 0% description coverage, so the description must compensate. It does not add any meaning beyond the schema—no explanation of what 'path' represents (e.g., file path, URL, format) or constraints. However, with only one parameter, the baseline is higher, but the description fails to provide additional semantic context, resulting in a minimal viable score.

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 specific action ('Read and extract text content') and resource ('from a PDF file'), distinguishing it from sibling tools like get_pdf_metadata (metadata only), read_pdf_page (single page), and search_pdf (search within). It precisely defines the tool's function beyond just restating the name.

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 implies usage for extracting full text and metadata from PDFs, but does not explicitly state when to use this tool versus alternatives like read_pdf_page for specific pages or search_pdf for targeted content. No exclusions or prerequisites are mentioned, leaving usage context somewhat open to interpretation.

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