set_join_mode_tool

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the mutation ('Set join_in_mode') without revealing side effects, whether a previous join mode is overwritten, reversibility, or required project state. The trailing '(TOOL_TIMEBASE: na)' fragment is unexplained noise and adds no behavioral context.

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?

One short sentence that front-loads the verb and packs the key modes efficiently. The '(TOOL_TIMEBASE: na)' suffix appears to be a template artifact that could confuse, which costs it the top score.

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?

Even though the tool is simple and an output schema exists, the description omits essentials: what project_path expects, how to obtain clip_id, and how this tool relates to sibling join tools. For a 3-param tool with zero annotations and 0% schema coverage, this is insufficient.

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 description coverage is 0% and no enums are defined, so the description is the only source of parameter meaning. It usefully documents the allowed values for join_in_mode (fade | crossfade | cut), but project_path and clip_id are entirely unexplained — no format, source, or relationship is given.

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 ('Set join_in_mode on one clip') plus the exact allowed values (fade | crossfade | cut). The 'one clip' qualifier loosely differentiates it from batch join tools like fade_joins_tool and crossfade_joins_tool in the sibling list, though it doesn't explicitly name them.

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?

Provides no guidance on when to choose this tool over closely related siblings such as fade_joins_tool, crossfade_joins_tool, or set_clip_fade_tool. There is no mention of prerequisites (project loaded, clip exists) or conditions favoring this tool. With roughly a hundred siblings, the absence of routing guidance is a real gap.

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