discover_all_clips

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

With no annotations, the description must fully convey behavioral traits. It only states the action ('List') without disclosing whether it is read-only, what happens if the track or slots are invalid, or any side effects. The lack of such details limits transparency.

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 concise: one sentence plus a short parameter list. It front-loads the purpose and adds necessary parameter info without extraneous text. Could be slightly more compact but currently efficient.

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?

Given that an output schema exists (though not shown), the description adequately covers the tool's basic function. However, it lacks specificity about whether empty slots are included, the structure of the returned data, or constraints like track existence. It is minimally 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?

Since the input schema has no descriptions (0% coverage), the description adds meaning by explaining each parameter: track_index as 0-based and max_slots as the maximum number of slots to check with default 20. This provides useful context beyond the raw schema, though still minimal.

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 uses a specific verb ('List') and resource ('all clips in a track's Session View slots'), making the tool's purpose unmistakable. It clearly distinguishes from sibling tools like get_clip_info (which targets a specific clip) or has_clip (which checks existence).

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 description provides no guidance on when to use this tool versus alternatives such as get_clip_info or has_clip. It does not mention when to choose this tool or any preconditions like requiring a valid track index.

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