get_job

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

Description only says 'poll', implying repeated calls, but does not disclose idempotency, error behavior, or rate limits. No annotations provided, so full burden falls on description.

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?

Single 5-word sentence is concise but under-specified. Lacks important details for an effective tool description.

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?

Despite having an output schema, the description does not hint at return values (e.g., job status, progress). Lacks context on polling behavior, making it incomplete for an asynchronous job polling tool.

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 coverage is 0% with no parameter descriptions, and the tool description adds no meaning beyond 'job_id' being a string. No elaboration on job_id format or constraints.

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?

'Poll an asynchronous scene job' uses a specific verb (poll) and resource (asynchronous scene job), clearly distinguishing it from siblings like cancel_job or update_action.

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?

No guidance on when to use this polling tool versus alternatives, no mention of polling frequency or when to stop polling.

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