doc2x_parse_pdf_submit

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

With no annotations, the description carries the behavioral disclosure burden. It usefully says this creates a task, returns a uid, and that progress should be monitored via status, but it does not mention permissions, upload side effects, failure behavior, or whether duplicate submissions are handled.

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 are front-loaded with the core action, return value, and sibling routing. There is no wasted text, and the usage caveat about doc2x_parse_pdf_wait_text is placed after the primary action.

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?

For a simple two-parameter async submit tool with full schema coverage and no output schema, the description gives the essential action, return value, and next-step routing. It could be slightly more complete by explicitly tying the returned uid to doc2x_parse_pdf_status, but it is otherwise sufficient.

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 both pdf_path and model are already well documented in the schema. The description adds only that this is for a local file and that the result is a uid, without adding parameter-level meaning 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 states a specific verb and resource: create a Doc2x PDF parse task for a local file. It also states the immediate return value ({uid}) and explicitly distinguishes this submit step from monitoring via doc2x_parse_pdf_status and doc2x_parse_pdf_wait_text.

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?

It explicitly routes monitoring to doc2x_parse_pdf_status and restricts doc2x_parse_pdf_wait_text to cases where the user explicitly asks to wait or return merged text. The intended use is clear: submit the local PDF first, then monitor through the named alternatives.

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