MCP PDF Reader

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states what the tool does (extract text) but doesn't mention performance characteristics (e.g., speed, memory usage), error handling (e.g., what happens with invalid page numbers), output format (e.g., plain text, structured data), or limitations (e.g., maximum file size, encrypted PDF support). This leaves significant gaps in understanding how the tool behaves in practice.

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 a single, efficient sentence that immediately conveys the core functionality. Every word earns its place - 'Extract text' specifies the action, 'from specific pages or page range' defines the scope, and 'in a PDF' identifies the resource type. There's no wasted language or unnecessary elaboration.

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 tool with 3 parameters, no annotations, and no output schema, the description is insufficiently complete. While concise, it doesn't address important contextual aspects like what format the extracted text returns in, whether it preserves formatting, how it handles errors, or performance considerations. The agent would need to guess about these operational details.

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 100%, so the input schema already documents all three parameters thoroughly. The description adds minimal value beyond the schema - it implies page range functionality but doesn't provide additional context about parameter interactions or edge cases. This meets the baseline for high schema coverage.

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 text') and resource ('from specific pages or page range in a PDF'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'read_pdf' (which might extract all pages) or 'search_pdf' (which might search within text), leaving some ambiguity about when to choose this specific extraction tool.

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 provides no guidance on when to use this tool versus alternatives like 'read_pdf' (for full extraction) or 'search_pdf' (for targeted searches). It mentions 'specific pages or page range' which implies partial extraction, but doesn't clarify if this is more efficient or appropriate than using other tools with filtering parameters.

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