submit_parse_batch

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

No annotations are provided, and the description is too brief. It does not disclose behavioral details such as return format (probably a batch ID), polling mechanism, error handling, rate limits, or required permissions. For an async operation with 8 parameters, this is insufficient.

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 sentence with no wasted words, but it is too minimal. It lacks structure and important details, making it efficient but under-specified.

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 complexity (8 parameters, async batch, output schema exists), the description is severely incomplete. It does not mention the output or how to check batch status (siblings like get_parse_batch_status exist but are not referenced). The agent lacks critical context for proper usage.

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 description coverage is 0%, meaning the input schema provides no meaningful descriptions for parameters. The tool description does not mention any parameters or their semantics. Thus, the agent receives no guidance on how to set parameters like use_ocr, ocr_engine, webhook_url, etc.

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 submits multiple PDFs for async batch parsing via /api/v1/pdf/batch. It uses a specific verb ('submit'), resource ('multiple PDFs'), and mode ('async batch'), distinguishing it from siblings like submit_parse_job (single) and parse_pdf_sync (synchronous).

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 explicit guidance on when to use this tool versus alternatives. The description implies batch processing, but does not contrast with siblings like submit_parse_job or parse_pdf_sync. The agent must infer usage from the tool name and context.

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