delete_ava_conversation

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

Annotations already declare destructiveHint=true, so the description's mention of deletion aligns. However, no additional context is added (e.g., irreversibility, required permissions, or side effects). The description meets the baseline but does not enhance transparency beyond annotations.

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 first sentence ('Interact with Ava...') is redundant and not specific to deletion, adding unnecessary fluff. The core purpose is in the second sentence. While short, it could be more concise and focused.

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 simplicity of the tool (2 params, no output schema, annotations present), the description covers the basic functionality. However, it omits any details about the result of deletion (e.g., success/failure indication) or potential side effects, making it somewhat incomplete.

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 description explicitly ties the conversationId parameter to the object being deleted ('by its ID'), adding meaning beyond the schema's bare string type. The customerContext parameter is already described in the schema. This provides sufficient context for both parameters.

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 ('Deletes') and the resource ('Ava conversation'), making it easy to distinguish from sibling tools like ask_ava_streaming or ava_feedback. The verb and target are specific.

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 (e.g., not mentioning that it's for deleting completed conversations). There is no advice on prerequisites, permissions, or scenarios where deletion is appropriate.

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