Run ExtendScript (advanced)

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

The description goes beyond the destructiveHint annotation by explaining the dryRun feature and the necessity of confirm flag. It adds context about power and destructiveness. No contradiction with annotations.

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?

Three sentences, front-loaded with the most critical information (escape hatch, power, return value). Every sentence earns its place; no wasted words.

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?

Even without an output schema, the description states the return format ('return its value as JSON'). Covers safety, execution control, and distinction from siblings. Fully adequate for a well-documented 4-param tool.

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?

Input schema has 100% coverage with descriptions. The description reinforces the safety parameters (confirm, dryRun) by explaining their roles in execution. This adds value beyond the schema definitions.

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?

Clearly states it runs an arbitrary ExtendScript snippet and returns JSON. Distinguishes from dedicated tools by labeling itself an 'ESCAPE HATCH'. The verb 'run' and resource 'ExtendScript' are specific.

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?

Explicitly says to use when no dedicated tool exists ('Prefer the dedicated tools when one exists'). Requires confirm:true to execute and recommends dryRun:true for preview. Provides clear when-to-use and safety instructions.

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