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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds real value on top: partial results are returned while running, what fields come back (GPU runtime, server timings), and the terminal-state set. The only gap is it doesn't explain error behavior for an invalid or foreign job_id.

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 the resource, then return contents, then polling rules. Every sentence carries information; the only minor friction is referencing poll_after_seconds, a response field that appears nowhere in the schema or description context.

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 does a good job sketching return contents and terminal states, and annotations cover the safety profile. It falls short only on parameter-level essentials (job_id shape, access_token) that an agent must get right to call the tool successfully.

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 0% and neither of the two parameters is described: neither the job_id format (the schema carries a strict ^studio_[a-f0-9]{32}$ pattern that an agent could easily violate) nor the purpose of access_token ("your own" hints at ownership scoping but doesn't say it). The description does not compensate for the coverage gap.

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+resource ("Read your own chat/image job") and enumerates what the read yields (partial text, final text or image availability, GPU runtime, server timings). It implicitly separates itself from submit_* siblings and from get_studio_image by framing this as job-status reading, though it never names those siblings explicitly.

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 operational guidance: poll with poll_after_seconds between checks and stop on succeeded/failed/expired, which is exactly the loop an agent needs. It also bounds scope with "Does not create or retry work," routing creation/retry elsewhere, though it does not name the specific alternative tools.

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