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

The annotations already establish that this is a safe, idempotent read. The description adds meaningful behavioral detail beyond them: the status lifecycle, the approximate drawing time, the distinction between price.credits and charged, and what extras represent. It remains somewhat cryptic, but it provides substantial context not present in structured fields.

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?

The description is compact and avoids filler, but it is written as dense fragments and awkward run-ons. The status list and field explanations are informative yet not front-loaded with a clear purpose statement. It is concise but harder to parse than it needs to be.

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?

There is no output schema, so the description carries the burden of explaining returned values, and it does so for statuses, sheet.url, price.credits, charged, and extras. It is fairly complete for a status-reading tool. It could still be clearer about where request_id comes from and how this tool fits alongside list_character_requests.

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 100% and the single required parameter request_id is documented in the schema. The description does not mention request_id or add any meaning beyond the schema. With one fully documented parameter, the baseline of 3 is appropriate.

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 name and title imply retrieving a character request, and the description explains what its status and output fields mean. However, it opens with return-value fragments rather than an explicit verb+resource statement, so the core action is inferred instead of stated. It does distinguish one sibling, draw_character_sheet, by noting it redraws the character as a base sheet.

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?

The description implies this is used to check progress, since it documents analyzing, drawing, drawn, and failed states and notes drawing takes about a minute. It also points to draw_character_sheet for redrawing as a base sheet. It does not explicitly say when to use this versus list_character_requests, wait_for_video, or other alternatives.

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