execute_extendscript

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

No annotations are provided, so the description carries full burden. It mentions 'full access to the app/qe DOM' and 'shell,' implying power and risk, but lacks explicit warnings about potential crashes, irreversible changes, or performance impact.

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?

Two front-loaded sentences with zero waste: the first defines the action and scope, the second adds usage restrictions.

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 single-parameter tool with no output schema, the description is adequate but could benefit from adding details about return values, error handling, and safety notes, given the tool's power.

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 input schema has 0% description coverage for the single required parameter 'script.' The description adds 'ExtendScript (ES3 JavaScript)' but does not clarify whether it expects a code string, file path, or anything about syntax, encoding, or limits.

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 'Run arbitrary ExtendScript (ES3 JavaScript) inside Premiere Pro' — a specific verb and resource — and distinguishes it from siblings by noting it's for 'anything the other tools don't cover.'

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 description explicitly says 'Use sparingly and only when a dedicated tool doesn't exist' and compares it to 'a shell into the running Premiere Pro instance,' giving clear when-to and when-not-to guidance.

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