open_in_source

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. It only says 'Premiere Pro expanded operation: open in source,' which is a vague label rather than an explanation of side effects, required state, or what happens when the tool executes.

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 short, but not meaningfully concise: 'Premiere Pro expanded operation' is filler, and 'open in source' merely repeats the tool name. It is under-specified rather than efficiently informative.

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?

With no annotations, no output schema, and no parameter details, the description is the only source of context, yet it provides almost none. An agent cannot determine what 'source' means, what gets opened, or how this differs from the many related source-monitor tools.

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 tool has 0 parameters, so there is nothing for the description to clarify about parameter meaning. The schema is trivially fully covered, and the baseline for zero-parameter tools is high.

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 is essentially a restatement of the tool name: 'open in source' adds no object or resource. It does not say what is opened (a clip? a project? the source monitor?) and does not distinguish it from siblings like get_source_monitor_info or insert_from_source.

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 given about when to use this tool versus alternatives such as close_source_monitor, play_source_monitor, or overwrite_from_source. There is no context about prerequisites, expected selection state, or typical workflow placement.

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