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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses two genuinely useful behavioral traits: links are private and short-lived, and ready download links do not consume credits. This adds cost and lifetime semantics an agent cannot get from the annotations, though it says nothing about refresh or rate limits.

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?

Two short sentences, front-loaded with the returned content and followed by the privacy/cost caveats. Nearly every clause earns its place, though the initial list is slightly run-on and would read better as a single enumerated statement.

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?

An output schema exists, so return values need not be spelled out, and the annotations already cover the read-only safety profile; the description usefully adds link privacy, link lifetime, and credit behavior. The only real gap is identifying the project_id argument, which is left entirely to the schema.

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 mentions the single required project_id parameter, its UUID format, or what kind of project identifier is expected. With a low-coverage schema, the description should compensate and instead adds no parameter meaning at all.

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 names a clear verb ('Read') and enumerates the concrete payload it returns: edits, generations, original/preview playback, and available downloads. That is specific about the resource content, though it never names 'project' directly and does not differentiate itself from structurally similar siblings such as get_batch or get_job.

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?

Usage is only implied. The note that 'Ready download links do not spend credits' hints at a decision rule against the credit-spending quote_/prepare_ export siblings, but the description never says when to call this versus list_projects or prepare_export. No explicit preconditions or exclusions are given.

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