list_clips

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 states 'List all clip slots' which implies a read-only operation, but does not explicitly confirm no side effects, required permissions, or other behavioral traits. Adequate for a simple read tool but lacks explicit 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 a single, front-loaded sentence that conveys the essential purpose without any wasted words. Every word earns its place.

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 the tool's simplicity (one parameter, no annotations, output schema present), the description provides a minimal but adequate overview. It does not explain what the output contains (though output schema covers that), nor does it mention prerequisites like track existence. Acceptable for a basic list operation.

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 input schema has one parameter ('track_index') with 0% description coverage in the schema. The description does not mention the parameter at all, leaving the agent to infer its meaning and any constraints (e.g., zero-indexed, valid range) solely from the parameter name. This is insufficient.

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 clearly states the tool's purpose: 'List all clip slots for a track, showing which slots have clips.' It uses a specific verb ('list') and resource ('clip slots for a track'), and distinguishes itself from siblings like 'create_clip', 'delete_clip', and 'get_clip' by focusing on enumeration of slots.

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 implies usage (when you want to see which slots have clips), but does not explicitly state when to use this tool versus alternatives like 'list_arrangement_clips' or 'get_clip'. No exclusions or conditions are provided.

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