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

Annotations already flag readOnlyHint=false, openWorldHint=true and idempotentHint=false, so the mutation profile is covered. The description adds genuinely new behavior: the bounded 15s wait, the exact timeout response shape (parsing_in_progress: true plus document id), and the reassurance that the document is accepted and continues parsing rather than failing — the key fact an agent needs to avoid a duplicate re-upload.

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?

Three sentences, front-loaded with the action, then the blocking behavior, then the failure path. No filler and no restatement of the title.

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?

There is no output schema, and the description does cover the partial/timeout return shape, which is the most important outcome. It does not describe what a successful parsed response contains, leaving the agent to infer the success payload.

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 every parameter including content_base64 and metadata is already documented. The description's base64 note restates the schema rather than adding format, size, or encoding constraints, so baseline 3 applies.

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?

Names a specific verb and resource ('Upload one document to an Airparser inbox') plus the distinguishing mode ('sync' with a bounded wait), which separates it cleanly from get_document and list_documents siblings. An agent knows exactly what the call does without opening the schema.

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 15-second wait and the parsing_in_progress fallback implicitly tell the agent when this call is appropriate, but the description never states when to prefer it over an alternative or what to do after receiving parsing_in_progress (e.g. poll get_document). No sibling tools are named.

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