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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description contributes only that the read covers a 'selected source range' and workflow/delivery info, adding modest context but no auth, pagination, or scoping behavior.

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 tight sentence with no waste and the resource and scope front-loaded. It is efficient, though very sparse for a tool with two parameters and several near-identical siblings.

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 needn't be described, and the annotations cover the safe-read profile, making the bare description minimally workable. Still, it omits clipId semantics and any disambiguation from clips_get, leaving the agent to guess when this differs from the other clip read tools.

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 50% and the required `clipId` has no description at all, nor does the description clarify its format or how it relates to `workspaceId`. The description provides no parameter meaning beyond what the (partially documented) schema shows, so it fails to 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?

States a specific verb (Read) and resource (one managed clip) and enumerates the facets returned: selected source range, project, workflow state, delivery information. However, it never distinguishes this from the very similar sibling `clips_get` (nor `clips_status_get`), so an agent cannot tell the two apart from the description alone.

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?

No when-to-use guidance, no prerequisites, and no reference to alternatives such as clips_get, clips_list, or clips_candidates_list. Given how many clip-related siblings exist, this absence is a real gap.

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