Launch Premiere

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

The description discloses the launch behavior, optional project opening, and waiting mechanism, which adds detail beyond the openWorldHint annotation. It does not contradict annotations. Some information about return behavior or idempotency (if app already running) is missing.

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 concise, front-loaded sentences. The first states the primary action, the second covers optional behaviors and a prerequisite. No redundant information.

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 simple launch tool, the description covers main actions and constraints. It does not specify return values (no output schema) or behavior when app is already running, but these gaps are minor given the tool's simplicity.

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 coverage is 100%, but the description enriches parameter meaning: 'absolute .prproj path' clarifies projectPath, and 'Poll the bridge for up to N seconds' explains waitForBridgeSeconds behavior. This adds value beyond the schema descriptions.

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 the tool's primary action ('Start Adobe Premiere Pro') and specifies optional behaviors (open project, wait for bridge). It distinguishes from siblings like premiere_open_project (which targets already-running instances) and premiere_quit.

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 provides context for when to use optional parameters (projectPath, waitForBridgeSeconds) and a prerequisite for waiting (bridge panel auto-open). However, it does not explicitly state when to use this tool vs alternatives like premiere_open_project, leaving some inference to the agent.

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