remove_all_notes

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'Remove all notes from a clip' but does not disclose that this is a destructive, irreversible action, whether it can be undone, or what happens to the clip's state. No side effects or safety implications are mentioned, which is a significant gap for a mutation tool.

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 concise and front-loaded with the main action. The parameter list is unambiguous and directly relevant. However, it could arguably omit the explicit 'Parameters:' section since the schema already presents them, but the added clarity for index meanings justifies 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?

For a tool with no annotations, no output schema, and only two integer params, this description is under-specified. It does not explain the difference from similar tools (e.g., remove_notes), does not mention whether the operation is reversible, and provides no context about expected behavior or carveats. The agent would have to infer these details from elsewhere.

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?

Since schema description coverage is 0%, the description compensates by explaining that track_index is 'the index of the track containing the clip' and clip_index is 'the index of the clip slot containing the clip'. This adds meaning beyond the bare parameter names and types in the schema, though it is minimal.

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 function: removing all notes from a clip. It includes the specific resource (clip) and the scope (all notes), which distinguishes it from sibling tools like remove_notes (which may remove specific notes) and quantize_clip_notes.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., clip must exist), no exclusion criteria, and no reference to sibling tools like remove_notes or clear_clip_automation. The description simply states the action without usage context.

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