delete_episode

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

The description adds behavioral context beyond annotations by stating 'Ownership is enforced when agent_id is provided,' which details a conditional security behavior. The annotations already indicate destructive and idempotent, so this complements them well. However, it doesn't disclose error handling or side effects.

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 at two sentences, with the main action front-loaded. Every sentence adds value without redundancy. It is well-structured for quick parsing.

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 simple delete tool with comprehensive annotations and schema, the description covers the core action and a key behavioral condition. It omits return values or error scenarios, but the lack of an output schema and the simplicity of the tool make this acceptable. Slightly more detail could improve completeness.

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 already provides detailed descriptions for both parameters (ownership verification and episode ID). The description's mention of ownership enforcement slightly reinforces the schema but adds no new semantic meaning. With 100% schema coverage, the description does not significantly enhance parameter understanding.

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 ('Delete') and the resource ('a single episode by ID'), providing a specific verb and resource. While it doesn't explicitly differentiate from siblings like 'archive_episode', the unique verb 'delete' and the specificity of 'by ID' make the purpose unambiguous.

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 offers no guidance on when to use this tool versus alternatives like 'archive_episode' or other sibling tools. It mentions ownership enforcement but does not explain under what circumstances one should choose delete over other operations. No 'when-to-use' or 'when-not-to-use' conditions are provided.

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