get_source_monitor_clip

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

With no annotations, the description carries the full behavioral burden. It implies a read via 'Get', but never states that the operation is side-effect free, what happens when the Source Monitor is empty, or what information is returned — and no output schema exists to fill that 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 no filler, and the scoping qualifier lands at the end where it is still easy to parse. It is efficient but extremely sparse for a tool whose return value is undefined.

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 no-parameter, no-output-schema tool, the description should at least hint at what 'info' is returned (name, in/out points, media path) and the empty-monitor behavior. Without annotations or an output schema, that omission leaves an agent guessing about the result shape.

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 takes zero parameters, so the baseline is 4; the description correctly requires no argument explanation and does not falsely imply any inputs.

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 and resource ('Get info about the clip') and scopes it precisely to the Source Monitor, which naturally separates it from get_clip_info (timeline clips) and get_active_sequence. It stops short of naming any sibling explicitly, so an agent must infer the distinction rather than being told.

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 Source Monitor scoping implies when the tool applies, but there is no explicit when-to-use guidance, no mention of prerequisites (e.g. a clip must be loaded via open_in_source_monitor), and no pointer to alternatives such as get_clip_info for timeline selection.

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