process_pdf

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It lists operations but omits critical details such as how path and data inputs are resolved (precedence or mutual exclusivity), error handling, and behavior when neither input is provided. This is a significant transparency gap for a composite tool.

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 compact and well-structured, starting with a clear overview followed by a brief parameter list. It is front-loaded and avoids verbosity, though the parameter section could be slightly expanded without losing 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's composite nature and lack of annotations, the description is adequate but incomplete. The output schema covers return values, but the description does not address input conflict resolution or provide usage context relative to siblings. The absence of annotations raises the bar for behavioral disclosure, which the description only partially meets.

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 description manually explains all parameters: path as absolute filesystem path, data as base64-encoded bytes, and pages as optional 0-indexed list. This adds meaning beyond the schema's bare type/nullable definitions. However, it does not clarify the relationship or precedence between path and data, which is a minor omission.

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's full scope: 'detect type, extract text, and convert to Markdown.' This specific verb+resource combination distinguishes it from sibling tools like extract_text or detect_pdf, making the purpose unmistakable.

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 the tool is for combined PDF processing but does not explicitly state when to use it instead of siblings. No alternatives or exclusions are mentioned, leaving usage context inferred from the listed operations.

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