AI-Process Order

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It reveals the async behavior ('202 + Location poll'), the output file ('saves process_order.json'), and nuanced parameter handling such as doc_name not being overwritten by the server and profiles being trimmed/omitted/wrapped. These are non-obvious traits that go well beyond what the schema conveys.

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 dense and well-structured, front-loading the purpose and then detailing the JSON body, parameter behaviors, and response handling. Every sentence provides non-obvious implementation details, with 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?

Given the lack of annotations, output schema, and parameter documentation, the description is largely complete: it covers input requirements, request body construction, polling behavior, and the saved output file. However, it does not clarify output_dir semantics or describe the structure of the extracted order data, leaving minor gaps.

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%, so the description must compensate. It explicitly explains doc_name (sent as docName or defaulted from pdf_file_path), pdf_file_path (local file types accepted), and profiles (trim, omit, wrap logic). However, output_dir is never mentioned, leaving its purpose and relationship to the saved file ambiguous.

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 'extract structured order data via PDF4me POST /api/v2/ProcessOrder', which is a specific verb+resource pair. This differentiates it from sibling process_* tools like process_invoice or process_receipt by focusing on 'order data', though it does not elaborate on what constitutes an order or the exact output structure.

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?

No guidance is provided on when to use this tool versus the many sibling process_* tools. The description gives detailed invocation instructions but omits any decision context, such as 'use for purchase orders' or exclusions relative to alternatives like process_invoice.

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