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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is given; the description still adds real value by scoping the read to a single account-owned request_id and stating no retry/starter side effects. It omits the status vocabulary the response can return, which matters since there is no output schema.

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?

Three tight sentences ordered trigger → scope/limits → next step, with zero filler. The anti-hallucination guard is placed last where it is most likely to be read before acting.

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 two-parameter polling tool with no output schema, the description covers when to call, what it will not do, and what to do on completion. The remaining gap is that it never enumerates possible status values, so an agent must infer how to interpret the response body.

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 description coverage is 0%, so the description must carry parameter meaning; it does explain that request_id identifies one existing request and is account-scoped. The lang parameter is never mentioned in the description and has no schema documentation, leaving one of two parameters unexplained.

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 — read-only, account-scoped status for one existing request_id — and explicitly carves out what it is not (does not start or retry generation). It also names the sibling (aimixer_result) that produces the actual output, so an agent can separate polling from retrieval.

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 concrete triggers ('is it ready?', generation in progress, a lost paid submit response), an explicit exclusion ('does not start or retry'), and the exact hand-off condition ('when status is complete, call aimixer_result'). The closing instruction not to invent a wait time or generate a substitute image closes the most likely misuse path.

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