parse_pdf

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It mentions supported formats and backend behaviors (e.g., MLX acceleration on Apple Silicon) but does not disclose output format, error handling, or any potential side effects. This is a moderate level of transparency—better than nothing but not comprehensive.

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 concise and front-loaded: two sentences quickly state what the tool does, then add context about backends and use cases. There is no redundant or filler content. The minor oddity of 'vunknown' does not affect conciseness.

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 has six parameters and no output schema, the description covers the core functionality, supported input types, and backend options, which is largely sufficient for an agent to understand the tool's role. However, it does not explain return structure or potential limitations, leaving small gaps. Still, it's fairly complete for a parsing tool.

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 all parameters are already fully documented in the input schema. The description adds no new semantic details beyond repeating that PDF/JPEG/PNG files are supported and that tables/formulas are extracted, which are already present in the schema property descriptions. Baseline of 3 is appropriate.

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 tool parses PDF and image files to extract text, tables, formulas, and structure. The specific verb 'Parse' and the listed resource types distinguish it from the sibling tool list_backends, making its purpose unambiguous.

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 clear context on when to use this tool—for documents, screenshots, photos, and scanned images—and notes backend options including Apple Silicon acceleration. However, it does not explicitly mention exclusions or compare against list_backends, so it's not a 5, but it offers sufficient guidance.

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