tosea_wait_for_document_parse

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

With no annotations, the description clearly states the polling behavior and terminal conditions. However, it does not describe backoff mechanism, rate limiting, or blocking nature, which are partially inferable from schema parameters.

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, well-structured sentence that is front-loaded with the key action. No extraneous information.

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 lacks details on return value, error states, or timeout handling. For a complex polling tool with multiple parameters and no output schema, more context is needed for correct agent 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 description adds no information about parameters beyond the input schema names. Given 0% schema coverage, it fails to explain parameter purpose, valid values, or behavior.

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 polls a document parse job until it reaches a terminal state (completed, failed, or cancelled). It distinguishes from siblings like tosea_get_document_parse (single check) and tosea_create_document_parse (initiation).

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 implies usage after creating a parse job, but does not provide explicit when-to-use or when-not-to-use guidance. It lacks mention of alternatives like synchronous wait or single status check.

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