Get Job Status

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds polling interval and completion behavior. No contradictions; it aligns with annotation hints.

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?

Concise, front-loaded summary followed by bullet points for usage details. Every sentence is informative.

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 existence of an output schema, the description appropriately focuses on usage and behavior. Minor gap: lacks guidance on timeout or handling errors (e.g., if status never reaches terminal state).

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 has one required integer parameter (job_id) with 0% description coverage. The description explains job_id is returned by the preceding tools, adding context. It could clarify that job_id is an integer, but the schema already specifies type.

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 job until completion, names the specific preceding tools (document.process, dataset.build), and distinguishes from siblings by describing the data flow (passing IDs to job.result or dataset.export).

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?

Explicitly instructs to call repeatedly every 3-5 seconds until status is 'completed' or 'failed', and tells what to do with the returned IDs for different job types. No alternative usage is needed.

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