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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely non-obvious behavior: the state machine's semantics and the fact that a failed job means credits were returned. It still doesn't say whether repeated polling is expected or whether results persist, so it's not 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 tight sentences: the action first, then the state semantics, then the exclusion. No filler and nothing buried.

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 usefully enumerates the possible status outcomes, which is the key return-value information an agent needs. The remaining gap is the provenance/format of jobId, which leaves a small but real hole for a required parameter.

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?

The single parameter jobId has 0% schema description coverage and the description says nothing about it — not where the ID comes from (presumably studio_generate/studio_quote/studio_save) nor its format. With only one param, the description could easily have closed this gap and didn't.

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 (Read) and resource (a saved generation), and explicitly fences itself off from the sibling studio_generate with 'This does not start another generation.' An agent can distinguish it from studio_generate/studio_save without opening a 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?

The status enumeration (queued/planning/generating/saving = in progress, ready = result, failed = credits returned) tells the agent when this tool is the right call and what outcome to expect. It never names an alternative tool explicitly, so it falls short of a full when/when-not routing statement, but the negative clause covers the main confusion.

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