cassette_edit

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

No annotations provided, but description fully discloses behavioral traits: requires CASSETTE_DIRECT_EDIT=1, uses manual-editor command lane, needs expected_version, explains undo mechanism with cursorSequence. Discloses input format.

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?

Concise 3-4 sentences with front-loaded purpose and usage. Every sentence adds value; 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?

Given the tool complexity and existing output schema, description covers purpose, usage, prerequisites, and parameter hints. Sufficient for correct invocation.

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 0% coverage, but description adds meaning: input is always {"payload": {...}}, expected_version from last timeline read, tool_name 'undo' with input.cursorSequence. Does not explicitly map each parameter but provides significant context.

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?

Clearly states it is a 'surgical no-LLM timeline edit' and distinguishes from sibling cassette_run_job for big or creative briefs. Uses specific verbs like trim, text, delete, undo.

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?

Explicitly says 'Use for small named changes' and 'big or creative briefs go through cassette_run_job', providing alternative and context. Also advises to use after reading cassette_timeline.

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