remove_notes

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the basic operation and parameter meanings, lacking information on side effects, error conditions, or irreversibility. The agent is left unaware of important behavioral characteristics.

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 extremely concise: a single sentence explaining the tool's purpose, followed by a clean bullet list of parameter definitions. Every sentence provides necessary information with no redundancy.

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 tool with 6 parameters and no annotations, the description explains the basic operation and parameter details. However, it lacks information about preconditions (e.g., clip existence), return value (none indicated), and error scenarios. This leaves gaps for an agent to safely invoke the tool.

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 only provides titles with no descriptions (schema description coverage 0%). The description compensates by listing each parameter with a clear, semantic explanation (e.g., 'Start time in beats' for from_time). This adds meaning beyond the schema, though some parameters like track_index and clip_index have obvious meanings.

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 action (remove notes), the target (a clip), and the parameterization (within a specified range). This distinguishes it from sibling tools like remove_all_notes which removes all notes without range.

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 that the tool is used when you want to remove a subset of notes from a clip, but it does not explicitly state when to use it versus alternatives like remove_all_notes or delete_clip. No exclusions or alternative suggestions are provided.

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