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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds substantial detail beyond them: it stops a running search, revokes share links, removes results, deletes the transcript, and is irreversible. It also explains the preview/confirmation-token workflow, which is important behavioral context for a destructive operation.

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?

Three dense sentences with zero waste. The irreversible consequence and confirmation flow are front-loaded before the procedural detail, making the definition 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 mutation with no output schema, the description covers consequences, irreversibility, and the required two-step confirmation. Combined with the fully documented input schema and destructive annotations, an agent has enough information to call it correctly.

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 coverage is 100%, so the schema already documents all five parameters, including the confirmation_token workflow. The description reinforces that workflow but does not add meaning beyond the schema for uid, chat_id, list_id, or bearer_token, so the baseline 3 is 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 and resource, 'Permanently delete one of the user's chats,' and immediately lists the exact side effects. It distinguishes deletion from siblings like get_chat, rename_chat, and reset_conversation by emphasizing permanence and transcript removal.

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?

It gives clear procedural guidance for the two-step confirmation flow: first call returns a preview and token, second call happens only after user confirmation. It does not explicitly name alternatives such as get_chat for inspection or preview_automation_deletion, but the usage context is otherwise clear.

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