pdf_to_xml

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

With no annotations, the description carries the full burden of behavioral disclosure. It only mentions conversion capability, omitting important details such as authentication requirements (API key), potential asynchronous job behavior (suggested by sibling tools like wait_job_completion), or expected output/response format. The reference to scanned images hints at OCR but doesn't explain limitations.

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 a single, clear sentence followed by a reference link, making it very concise and front-loaded. No unnecessary words, though the reference link might be more useful in a separate documentation field, but it doesn't detract significantly.

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?

The tool has 11 parameters and no output schema, and the description does not explain the overall workflow (e.g., whether it returns a job ID for asynchronous processing), what the XML output looks like, or preconditions for the source URL. The schema covers parameters, but the description fails to tie together operational context, leaving significant gaps for an agent to correctly invoke and interpret results.

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 provides 100% parameter description coverage with detailed explanations for all 11 parameters, so the baseline is 3. The tool description adds no extra parameter-specific information beyond what the schema already provides, so it neither helps nor hurts.

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') with a clear resource ('PDF and scanned images') and target format ('XML'), immediately distinguishing it from sibling tools like pdf_to_json or pdf_to_text. No ambiguity about what the tool does.

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 does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. However, the explicit mention of 'XML format' implies it is the right choice when XML output is needed, providing minimal implicit guidance.

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