execute_extendscript

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

With no annotations available, the description must disclose behavioral traits like side effects, permissions, or return values. It offers nothing beyond the literal action, so the agent cannot anticipate consequences or requirements of executing an arbitrary ExtendScript.

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 brief, but this is under-specification rather than efficient conciseness. It uses a single sentence that adds no substantive information beyond the name, failing to earn its place by conveying useful context.

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?

The tool is an open-ended execution command with no annotations, no output schema, and an opaque parameter schema. The description provides none of the necessary context about what ExtendScript is, what it can do in Premiere Pro, or how the agent should invoke it, making it wholly inadequate for correct usage.

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 is an open object with no defined properties, and the description does not explain what the object should contain. While the schema technically has 100% coverage (zero parameters), the tool clearly requires some input, and the description fails to clarify the expected structure or semantics of that input.

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 'Premiere Pro expanded operation: execute extendscript' is largely a restatement of the tool name. It identifies the domain (Premiere Pro) and the action (execute extendscript) but does not clarify what executing an ExtendScript script accomplishes or how it differs from the many specialized sibling tools.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, scenarios, or any exclusion criteria, leaving the agent without direction for selecting this tool among dozens of siblings.

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