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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is established. The description adds meaningful detail by naming exactly which saved artifacts are cleared: queued candidates, processed handles, seed criteria, and kept leads.

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 front-loaded sentence with no filler. It leads with the action and then lists the affected data, which is efficient and easy to scan.

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 destructive reset with no output schema and fully documented parameters, the description gives enough information about what state is cleared. It could be stronger by clarifying whether the conversation itself persists and how it relates to delete_chat, but the core effect is sufficiently described.

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 the schema fully documents all five parameters, including conversation_id and preferences_mode. The description adds no parameter-level semantics beyond the schema, making the baseline 3 appropriate.

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 uses a specific verb, 'clear', followed by a concrete list of resources that are cleared, so the agent can understand the operation. However, it does not explicitly distinguish this state reset from siblings such as delete_chat or remove_leads, and 'MCP conversation' leaves some ambiguity about what conversation object is affected.

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 explains what is cleared but gives no guidance on when to use this tool, when not to use it, or which alternatives apply. With destructive siblings like delete_chat and remove_leads, the absence of routing guidance is a clear gap.

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