extract_selection

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

The description explains the behavior (remove and close gap) but contradicts the annotations: destructiveHint=false implies non-destructive, yet removing content is destructive. This contradiction undermines reliability.

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?

Single sentence, to the point, with no redundancy. Could be slightly improved with an example, but overall concise and front-loaded.

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?

Adequately describes the basic action, but lacks prerequisites (e.g., sequence must have in/out points set, active timeline) and does not mention return value or error conditions. For a simple tool without parameters, this is acceptable but not thorough.

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 no parameters, so schema coverage is 100%. The description adds no parameter info, which is acceptable as none exist. A higher score could be achieved if it explained that no parameters are needed due to reliance on sequence in/out points.

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 extracts (removes and closes gap) content between sequence in/out points, using a specific verb and resource. It distinguishes from siblings like lift_selection and ripple_delete, but could be more explicit.

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?

No guidance on when to use this tool versus alternatives such as lift_selection or ripple_delete. The description does not mention context or exclusions.

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