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

Beyond the annotations (destructive=true, idempotent=false), the description discloses meaningful traits: the "[write, queued]" tag, asynchronous worker dispatch, the QUEUED/DONE/FAILED state machine, and that image_project/image_output are merged rather than replaced. It does not say whether re-rendering overwrites an existing image_render or what auth scope is needed, which keeps it from a 5.

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 dense sentences that front-load the write/queued nature and the lookup keys before the workflow detail. Slightly cryptic bracket and arrow notation costs a little readability, but every clause carries information.

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 an async mutation tool with no output schema, the description supplies what the schema and annotations cannot: that the call returns immediately after queueing and that results must be read back via the image row's fields. Only permission/overwrite behavior is left unstated.

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 carries the burden and largely does: it identifies all four parameters, frames image_id and image_uuid as alternative lookup keys, and adds the crucial "merged" semantics for image_output/image_project. It still doesn't convey that at least one identifier is effectively required or what the object shapes look like.

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?

Specific verb + resource ("Queue the server-side render of an image") with the exact lookup keys named, plus the internal state transition (image_render_process=QUEUED -> worker_images_render). An agent can distinguish this from create_image, render_video, or update_image_keys without opening the schema.

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 states the post-call workflow clearly (poll image_render_process for DONE/FAILED and read image_render), which is real usage guidance, and notes the optional same-edit save. But it never says when to choose this over sibling render/create tools or what happens if a render is already queued — usage is implied rather than spelled out.

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