CPersona

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

Annotations indicate destructive and idempotent behavior. The description adds valuable auth context ('Ownership is enforced...') not present in annotations. However, it omits behavioral details like permanence of deletion or error handling for non-existent IDs.

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?

Two sentences with zero redundancy. The first sentence establishes the core operation; the second provides critical auth context. Efficiently structured with every sentence earning 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?

Covers the basic operation and ownership model, but given the destructive nature and presence of archive_episode as a sibling, it should clarify the hard-delete semantics and distinguish from soft-delete alternatives. No output schema exists, so return values don't need description.

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?

Input schema has 100% description coverage, establishing the baseline. The description reinforces the ownership aspect of agent_id and implies its optionality ('when provided'), but doesn't add substantial semantic depth beyond the schema definitions.

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'), resource ('episode'), and scope ('single episode by ID'). It distinguishes from siblings like list_episodes and delete_agent_data through specific resource naming, though it doesn't explicitly differentiate from archive_episode.

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 provides usage constraints ('Ownership is enforced when agent_id is provided'), implying authentication requirements. However, it lacks explicit guidance on when to choose this over archive_episode or other delete siblings.

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