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

The annotations already mark this operation as destructive=true, idempotentHint=false, and readOnlyHint=false, but the description adds nothing beyond what the annotations state. It does not mention that deletion is permanent, what gets deleted along with the conversation, whether confirmation is required, or what happens to associated messages and notes.

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 a single short sentence with no wasted words, but this is achieved by omission rather than by efficient expression. There is no warning or effect information to front-load.

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?

This is a destructive mutation with no output schema, but the description does not state whether the deletion is permanent or irreversible or what side effects it causes. That leaves the agent without the context it needs before performing a destructive operation.

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 description coverage is 100%, so both agentId and convoId are documented in the schema. The description adds no additional meaning to these parameters, which is the baseline when the schema already fully documents them.

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 simply restates the tool name and title, saying only 'Delete a conversation'. Although it is clear that the tool deletes a conversation, it does not distinguish this tool from siblings such as delete_conversation_note, update_conversation, or export_conversation.

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 gives no guidance about when to use this tool instead of alternatives, and no prerequisites or warnings. Usage is only implied by the word 'Delete'.

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