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

The description discloses the core behavior: base64 PDF input, Markdown output, and page-by-page sectioning. However, with no annotations provided, it carries the full burden and does not mention error handling, size limits, scanned-PDF behavior, or what happens beyond max_pages. It is adequate but minimal.

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?

A single, front-loaded sentence that captures the verb, input format, output format, and a structural detail. Every word earns its place and there is no filler or redundancy.

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 simple two-parameter converter with an output schema available, the description plus schema is sufficient for an agent to invoke it correctly: required pdf_base64 and optional max_pages are covered. The only minor gap is the absence of explicit guidance about when to choose this over sibling tools.

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%, and both parameters already have meaningful descriptions in the schema. The tool description restates 'base64-encoded bytes' but adds no operational detail beyond what the schema already provides, so the baseline 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 states a specific verb ('Convert'), a clear resource (PDF base64 bytes), and the exact output format (Markdown). 'One section per page' clarifies the output structure and helps distinguish this tool from siblings like ocr_image or parse_spreadsheet.

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 when to use it: whenever a PDF must be converted to Markdown. However, it does not explicitly mention alternatives or exclusions, such as using ocr_image for image-based documents or parse_spreadsheet for tabular files. Usage context is clear but left to inference.

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