play_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. It discloses only that playback occurs, omitting whether the source monitor must have media open, whether playback is asynchronous, or what side effects occur.

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 under-specified; most of it is boilerplate 'Premiere Pro expanded operation' that does not earn its place. It is effectively a restatement of the tool name with no added structure or detail.

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 tool with no annotations or output schema, this description leaves an agent without enough context to know when to call it, what preconditions exist, or what result to expect. Simple as the action may be, the definition is not complete.

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 no parameters and schema coverage is trivially 100%, so there is no parameter information for the description to add. The baseline for zero parameters 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?

The description 'Premiere Pro expanded operation: play source monitor' essentially restates the tool name play_source_monitor, adding only boilerplate. It communicates the basic action but does not distinguish this from siblings like play_timeline or open_in_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?

There is no guidance about when to use this tool versus alternatives such as play_timeline, stop_playback, or open_in_source. The description implies the action but gives no context or exclusions.

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