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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: media context is 'bounded' and signed media links go stale and must be refreshed by reading again. That is useful disclosure not available in the annotations or schema.

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 dense sentences with the returned-content list front-loaded and the refresh nuance last. No filler and 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?

An output schema exists, so return values need not be spelled out, and the description does summarize the payload. But for a tool with five required parameters and 20% schema coverage, the meaning of expectedRevision and the pagination contract are left entirely unexplained, leaving a noticeable gap.

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 only 20%, and the sole documented field is a generic 'UUID string.' The description never explains expectedRevision (a likely concurrency precondition), offset/limit pagination, or workspaceId. 'Bounded media context' only faintly gestures at limit/offset and 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?

The description gives a specific verb (Read) and resource (editor snapshot) and enumerates what it returns: current revision, stable timeline IDs, captions, style and bounded media context. That is far more concrete than a tautology. It doesn't explicitly contrast with siblings like editor_history_list, so it stops short of a 5.

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?

'...before a precise revision' implies the tool belongs at the start of an edit workflow, and the note that signed media links are refreshed by re-reading is a genuine usage hint. However, no alternative is named and no explicit when-not condition is given, so usage is only implied.

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