open_in_source_monitor

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

No annotations are provided, so the description carries the full burden, yet it says nothing about whether this replaces the currently loaded Source Monitor clip, whether it mutates project state, what happens if the node is not a media item, or what is returned. For an operation that changes UI/application state, this is a significant gap.

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?

A single, front-loaded sentence with zero waste. It is appropriately terse for a one-parameter tool, though it errs toward under-specification rather than excess.

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 one-parameter tool with no output schema, the description is minimally sufficient to identify the action. However, with no annotations and no mention of side effects on the Source Monitor or return behavior, it leaves meaningful behavioral questions unanswered.

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?

There is a single parameter (nodeId) with 100% schema description coverage, so the schema already documents its meaning. The description adds no additional detail about nodeId format or how to obtain it, so baseline 3 applies.

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?

States a specific verb (open) and resource (project item) plus the destination (Source Monitor), so the agent knows exactly what action is performed. It does not explicitly differentiate itself from related siblings such as get_source_monitor_clip or add_clip_to_timeline, but the action is unambiguous.

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?

There is no guidance on when to use this versus alternatives like add_clip_to_timeline, overwrite_clip_to_timeline, or set_active_sequence. The agent must infer that this only loads the item into the Source Monitor view without adding it to a sequence.

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