PDF MCP Server

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 adds valuable context about the backend ('Uses a Python backend (marker-pdf)') and its capabilities ('preserve mathematical notations (LaTeX) and layout structure'), which helps the agent understand the tool's behavior beyond basic functionality. However, it does not mention error handling, performance characteristics, or output format details.

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 appropriately sized and front-loaded, with three concise sentences that each add value: the core functionality, technical details, and usage context. There is no wasted text, and it efficiently communicates essential 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?

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is somewhat complete but has gaps. It covers purpose and backend details but lacks information on output format, error conditions, or performance limits. Without an output schema, the agent is left uncertain about what the tool returns, which is a significant omission for a read operation.

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 schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description does not add any additional meaning or context about the parameters beyond what the schema provides, such as explaining the significance of page ranges or path requirements. Baseline 3 is appropriate when the schema does the heavy lifting.

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'), with additional detail about the backend and target use case ('Best for scientific papers'). It distinguishes itself by mentioning preservation of mathematical notations and layout structure, which is valuable even without sibling tools.

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 context ('Best for scientific papers') but does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. With no sibling tools, the bar is lower, but it lacks comprehensive usage instructions.

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