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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavior: an identity/ownership requirement and a hard 24-hour retention window after which the resource is unrecoverable. It also discloses the return shape (an image content block), which annotations do not. It omits what happens on expired or not-yet-complete jobs.

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 short sentences, front-loaded with what is returned, followed by the auth prerequisite and the expiry constraint. No sentence is redundant with the annotations or the schema.

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?

With no output schema, the description correctly spends a line specifying the return type, and no annotations substitute for the retention and auth facts. The only gap for a 2-parameter retrieval tool is error behavior (expired job, wrong token, job still running).

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 compensate. It partially does by explaining the access_token must match the submitting identity, but job_id is never characterized beyond its regex pattern (where it comes from, whether a job or studio job id is expected) and the distinction between job_id and the token is left implicit.

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: it returns the completed image as an MCP image content block, which clearly separates it from metadata-oriented siblings like get_studio_job and get_compute_status. It never names a sibling explicitly, so the differentiation is inferable rather than stated.

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 the two conditions an agent actually needs: the same token/identity that submitted the job must be used, and the image must be retrieved within 24 hours. It does not say whether to poll get_studio_job for completion first or what to do if the job is unfinished, so it stops short of full when/when-not guidance.

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