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

With annotations already covering read/write safety, the description adds valuable behavioral detail: it returns a batchId immediately, is asynchronous, requires no saved processor, and applies an optional inline config to all runs. No contradiction with the annotations is present.

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?

Two sentences convey the core behavior, capacity limit, configuration model, asynchronous nature, and follow-up workflow with no filler. The most important facts are front-loaded.

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 description is sufficiently complete for an agent to invoke the tool and know how to retrieve results, especially since an output schema exists. It covers the async flow and batch semantics; minor omissions like explicit idempotency caveats are already represented by the annotations.

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 100%, so all parameters are already documented. The description adds context that the inline config applies to every run and that no saved processor is needed, but it does not substantially expand per-parameter semantics beyond the schema.

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 identifies the tool as submitting up to 1,000 documents as a batch of parse runs, distinguishing it from single-document operations like parse_document and from batch operations in other domains. It uses specific language: 'Submit', 'batch of parse runs', and 'parse group'.

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 states the batch submission use case and gives actionable follow-up guidance (poll get_parse_batch, fetch with list_parse_runs filtered by batchId). It does not explicitly exclude single-document cases or name parse_document as the alternative, but the context is clear enough.

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