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

Beyond the readOnly/idempotent annotations, the description discloses return behavior: items are oldest-first, only ten recent entries are kept, terminal states include DONE/FAILED/CANCELED, and failures surface an `error` while successes expose a picture `url`. It doesn't cover polling costs or permissions, but it adds substantial context the annotations don't.

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?

Dense but front-loaded: the `[read]` tag and the referenced producer tool come first, then field semantics. The single long sentence is run-on in places, but nearly every clause (ordering, terminal states, `left` 0, socket alternative) earns its place.

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 read tool with no output schema, the description effectively serves as the output contract: item fields, counters, recent-entry cap, terminal states, and completion signal are all spelled out. Nothing essential for correct invocation is missing beyond param documentation, which the name largely covers.

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% and the description never explains `character_uuid`, so the sole parameter is documented only by its self-evident name and the context that the queue belongs to 'a character'. Adequate but with a clear gap given zero schema coverage.

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 description states precisely what it returns: the production queue for a character created via queue_character_assets, including items, counters, and recent terminations. That distinguishes it from get_character, list_characters, and other character reads, though the phrasing opens with an awkward nominal ('The production of a character queued...') rather than a clean verb.

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?

It implicitly tells the agent to call this after queueing via queue_character_assets, gives a completion condition (`left` 0 means finished), and notes that open studio panels already follow the queue live via socket – useful when-to-use context. There is no explicit exclusions list, so it stops short of a 5.

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