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

With no annotations, the description carries the full behavioral burden; it does disclose the essential async contract (immediate return of request_id, later retrieval), which is the most important trait. It says nothing about whether the job can be cancelled, what priority=low actually changes, whether submission is idempotent, or what happens to the input on failure, so meaningful gaps remain for a mutation tool with zero annotation coverage.

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, zero waste, and the return-value contract is front-loaded before the follow-up instructions.

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?

No output schema exists, and the description compensates by naming the request_id return and the follow-up tools. However, the nested `input` object (free-form, additionalProperties) and the task-inference-vs-override behavior are left entirely unexplained, which is a real gap for a 5-parameter job submission 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 80%, with model, task, webhook, and priority already documented inline, so the schema does most of the work and the baseline of 3 applies. The description adds no meaning beyond the schema — notably it never explains the `input` object, which has additionalProperties and no documented shape.

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?

States a specific verb and resource ("Queue a request") and adds the key observable outcome (returns request_id immediately), which clearly distinguishes it from the polling siblings. It does not, however, distinguish it from run_model, the obvious synchronous alternative in the sibling list.

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 directs the agent to follow up with check_job / get_job_result, so the async workflow is unambiguous. Missing is any guidance on when to choose this over run_model, or when the webhook parameter removes the need for polling.

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