cascadeur_select_frames

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

Annotations already declare destructiveHint=true, so the agent is warned of mutating behavior. The description adds a temporal precondition but does not disclose what state changes occur (e.g., overwriting previous selection, clearing selections) or what exactly becomes destructive. No contradiction with annotations.

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 sentence that is front-loaded with the main action and includes the relevant usage context. No redundant words or padding, making it efficient and easy to parse.

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?

The tool has three required parameters with zero schema descriptions and no output schema, so the description must provide enough context to invoke it correctly. It fails to clarify essential parameter semantics and side effects, leaving an agent to guess at the meaning of 'first' and 'last.' The usage context alone is not enough for safe and correct use.

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%, so the description must compensate for the lack of parameter documentation. It only implies 'track interval' without explaining that 'tracks' specifies which tracks, or whether 'first' and 'last' are frame indices, inclusive/exclusive, or require ordering. This is insufficient for correct parameter filling.

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 identifies a specific verb and resource ('Select an explicit track interval') and states its intended context ('before physics, mirror, clipboard or timeline actions'). This differentiates it from sibling tools like cascadeur_select_objects or cascadeur_set_frame, though it doesn't fully define what a 'track interval' is.

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 gives clear contextual guidance by saying the selection should happen 'before physics, mirror, clipboard or timeline actions,' indicating when it should be used. However, it does not mention alternative tools or any when-not-to-use conditions, so it falls short of a 5.

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