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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only that results carry 'current workflow state'; it says nothing about pagination limits, filter behavior, or result ordering, so it adds limited value beyond the structured fields.

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 front-loaded sentence with no filler or repetition. Its only weakness is the compressed, undefined jargon ('bounded managed clips'), which costs a little clarity at the same word count.

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 described, and the annotations cover the read-only/idempotent profile. What remains missing is filter semantics for a six-parameter listing tool, particularly the undocumented status filter and pagination bounds, which an agent needs to call it correctly.

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 50%, and the covered fields are trivially documented as 'UUID string.' The description does not explain limit, offset, or the status filter at all, nor does it clarify how assetId/projectId/workspaceId scope the listing; the vague 'selected source or project' is the only hint and it is not tied to a named parameter.

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 (List) and resource (managed clips) plus scope (from the selected source or project) and a hint at returned data (current workflow state). It does not, however, distinguish itself from close siblings like clips_candidates_list or clips_presets_list, and the qualifier 'bounded managed' is unexplained jargon.

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?

There is no statement of when to use this tool versus clips_get, clips_inspect, clips_candidates_list, or clips_status_get, and no preconditions or exclusions. The phrase 'from the selected source or project' implies a context dependency but never says how that selection is made.

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