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

No annotations are provided, so the description carries the full burden. It does disclose real behavior beyond the schema: the ACCEPTED trigger, the running/polling loop, and the 20-second retry interval. However it never says what other status values mean (succeeded/failed/expired), whether jobs expire, or how long results persist, which matters for a polling tool.

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?

A single dense sentence that front-loads the identity (fast-workshop background result query), then the trigger condition, then the polling rule. No filler or repetition.

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?

For a one-parameter polling tool with no output schema and no annotations, the description covers the essential loop (ACCEPTED in, job_id, re-poll on running) but stops short of saying what the terminal result looks like or when polling should be abandoned, which the agent would need to avoid infinite polling.

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?

Only one parameter, and schema description coverage is 100%, so the schema already documents job_id as the value found in the ACCEPTED result. The description reinforces its origin and ties it to the ACCEPTED condition, adding light contextual meaning over the schema's own wording, hence just above the baseline.

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+resource combination in "查询转入后台的调用结果" (query the result of a background call) and scopes it to results that were deferred with code=ACCEPTED. An agent can distinguish this from siblings like task_status or publish_status because the trigger condition is spelled out.

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?

Gives explicit usage context: call it when some tool returns code=ACCEPTED, and poll again after 20 seconds if status=running. That is strong when-to-use guidance, but it never explicitly excludes or contrasts the sibling task_status/publish_status tools, so an agent facing overlapping status tools still has to infer which to pick.

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