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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds behavioral details: text-layer PDFs are read exactly (fidelity) and cost less, while images go through a vision model. This gives practical context about performance and output quality, though it does not detail failure modes or limits.

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 two sentences, front-loaded with the main purpose. The second sentence adds a concise cost/processing note. No redundant phrasing.

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 single parameter, clear annotations, and presence of an output schema, the description covers the core functionality and important behavioral traits. It lacks explicit alternatives or error scenarios, but those are outside the core completeness for a simple conversion 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 covers 100% of the single parameter (url) with a clear description. The tool description adds context about processing modes (vision model vs exact text) but does not add new parameter syntax or format details beyond what the schema already provides.

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 uses a specific verb ('Convert') and resource ('PDF or scanned page image') and specifies output ('clean Markdown') and key features (headings, lists, tables, multi-column reading order). This clearly distinguishes it from sibling tools like extract_tables and extract_statement.

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 for PDF-to-Markdown conversion but does not explicitly state when to prefer this tool over alternatives such as extract_tables. It provides input-type guidance (text-layer vs image) and cost note, but no exclusions or comparative alternatives.

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