convert_pdf

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

With no annotations, the description transparently discloses key behaviors: automatic PDF type detection, best extraction method selection, and return of confidence scores and warnings. This adds value beyond the schema, though it doesn't mention potential side effects or permissions.

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?

Two sentences, zero wasted words. Essential information is front-loaded: action, resource, then additional features. Highly concise.

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?

While purpose and output details are covered, the lack of parameter descriptions (especially for 'format' and 'quality') leaves the tool incomplete for effective use. An output schema exists but is not shown; description should compensate but does not.

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%, placing full burden on the description to explain parameters like 'format' and 'quality'. The description fails to provide any details about these parameters, offering no guidance on valid values or behavior.

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 ('Convert a PDF to AI-readable Markdown') and resource, distinguishing it from siblings like analyze_pdf or extract_streaming. The verb 'Convert' and target format 'Markdown' make the 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?

Implies usage for general PDF-to-Markdown conversion with automatic detection, but does not explicitly state when to use alternatives like extract_structured or batch_convert. No when-not or exclusions provided.

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