pr_setClipEnabled

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation. The description adds useful behavioral context beyond that: disabled clips stay on the timeline but do not render, which clarifies the effect of the operation.

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 a single front-loaded sentence with no wasted text, and the behavioral note is compactly placed in parentheses.

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 mutation tool with no output schema, the description plus annotations and schema provide enough context to invoke it correctly. Minor gaps remain, such as clip-not-found behavior, but they are not essential for basic use.

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 67%, and the schema itself documents clip targeting formats and the optional sequence parameter. The description does not add parameter-specific meaning beyond the operation concept, so a baseline score is appropriate for moderate schema coverage.

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 states a specific verb pair (enable/disable) and resource (clips), making the operation immediately identifiable. It does not explicitly differentiate from nearby siblings such as pr_setClipProperties or pr_clipOps, but the core purpose is clear.

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 parenthetical explains the outcome of disabling a clip—it remains on the timeline but does not render—which implies a use case for temporarily suppressing clips without deleting them. However, it does not name alternatives or state when to prefer other tools like pr_removeClips or pr_setClipProperties.

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