Premiere timeline

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's 'Run' adds little. It does not disclose any specifics about side effects, what gets modified or destroyed, permission requirements, or whether the action is reversible. With no annotation-provided detail beyond the hints, the description carries the burden and fails to elaborate.

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 extremely short, but it is under-specified rather than concise. It front-loads nothing useful and every word is generic. A well-structured description would lead with the core purpose and then explain parameters or usage; this provides neither.

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?

Given the tool's destructive hint, open-world hint false, six parameters with nested objects, and no output schema, the description is drastically incomplete. It does not explain what actions are available, how to construct targets or args, or what the expected response is. An agent would have almost no basis to call this tool correctly without external documentation.

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 0%, meaning the description must compensate for the six parameters, including actionId, args, target, approvalId, operationId, and expectedRevision. The description mentions 'typed ... action' but gives no explanation of what actionId should contain, how args/target are structured, or when approvalId/operationId are needed. An agent cannot infer how to populate parameters from this text.

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 verb ('Run') and lists a set of resource types ('sequence, track, clip, selection, marker, or transition action'), but the meaning of 'run' and the nature of these actions is entirely unspecified. It does not distinguish itself from sibling tools like premiere_project or premiere_media, which likely also involve executing operations. The scope is too broad and generic to give an agent a clear idea of what this tool actually does.

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 guidance on when to use this tool versus the many sibling tools. No mention of conditions, prerequisites, or alternative tools. The description provides zero context for an agent to decide if this is the right tool for a given task.

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