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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety and idempotency are covered. The description adds the useful workflow context that the revision must be passed unchanged to set_downloads, but doesn't mention pagination, permissions, or output shape.

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?

A single dense sentence enumerating outputs, plus a short second sentence on the revision handoff. Front-loaded and no fluff, though the field enumeration is long.

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?

For a simple read with one param, annotations, and no output schema, the description adequately explains what data is returned and the revision workflow. The only gap is version_id's meaning/format.

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% with only one parameter (version_id), which has no description. The description implies version-related context but never defines version_id or its format. Baseline for 1 undocumented param is 3.

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 specifies a clear verb (Read) and enumerates the exact resource fields it returns (download switch, attachments, labels, formats, sizes, candidates). This distinguishes it from siblings like get_replay_settings or read_version. However, it doesn't explicitly contrast with set_downloads/preview_downloads beyond the revision hint.

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?

It clearly states to use this before set_downloads by passing the revision back unchanged, which is actionable guidance. It doesn't explicitly rule out other tools or say when not to use it, and doesn't mention preview_downloads as an alternative.

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