select_region

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

With no annotations provided, the description carries the full burden. It explains the relationship to effects but omits critical behavioral details such as whether this replaces existing selections, affects cursor position, or validates that start < end.

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 efficiently structured with purpose first, followed by usage context, then an Args block. Every sentence earns its place with no redundant or verbose text.

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 two-parameter selection tool, the description covers the basics adequately but lacks completeness regarding selection state management (replace vs. add) and validation constraints that would help an agent avoid errors.

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?

Given 0% schema description coverage (only titles 'Start'/'End'), the description compensates effectively by specifying these are 'time in seconds,' providing essential unit information that the schema lacks.

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 opens with a specific verb ('Select') and clear resource ('time region in the current track(s)'), distinguishing it from sibling tools like select_all, select_clip, or select_tracks by specifying temporal bounds.

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 notes that 'Many effects operate on the selection,' implying this tool is used to scope subsequent effect operations. However, it lacks explicit when-not guidance or contrasts with alternatives like select_all or select_clip.

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