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

The description and readOnlyHint/idempotentHint consistently indicate a safe, read-only operation with no side effects. The explicit 'No transcript is available' warning adds clarity beyond the annotations, though error behavior is not described.

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?

The description is brief, direct, and front-loaded with the core purpose. Every sentence adds meaningful information without unnecessary detail.

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 tool, the description conveys the essential return content (metadata and description) and a key limitation (no transcript). It does not specify exact output fields, but the absence of an output schema makes this acceptable.

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 only parameter, id, is fully described as a video id or video_ archive id from List or Search. This gives the agent clear guidance on what value to supply and where it comes from.

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 clearly states a specific action ('Read') and resource ('metadata and description of one video'), and scopes it to videos already discovered by this instance. This distinguishes it from sibling tools like video_list and video_search, which operate at the collection level.

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 phrase 'already discovered by this instance' signals that this tool is intended for use after a list or search operation has returned a video id. It also adds a useful limitation ('No transcript is available') that prevents misuse, though it does not explicitly name alternative tools.

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