cassette_update_clip

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

No annotations provided, so description must cover behavior. It indicates mutation but omits details on error handling (invalid clipId), update semantics (merge vs replace), permissions, or side effects. Insufficient for safe agent use.

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, no redundancy, efficiently conveys core action without filler.

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?

No output schema, no annotations, and description is too brief. For an update tool with arbitrary updates object, more detail on behavior (merge vs replace, return value) and differentiation from similar tools (e.g., cassette_update_clip_notes) is needed.

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 has two params with 0% description coverage. Description adds examples of updateable fields (name, status, progress), partially compensating for missing schema descriptions. Does not explain clipId or updates structure explicitly.

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?

Description explicitly states the verb 'update' and resource 'clip fields', with examples (name, status, progress). Clearly distinguishes from siblings like create, delete, get, and list clips.

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?

Context implies use for modifying clip fields, with siblings covering creation, deletion, and retrieval. No explicit when-not or alternative suggestions, but clarity suffices.

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