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

Goes well beyond the destructiveHint annotation by naming what is destroyed (the conversation on LinkedIn itself), that it is irreversible, and that it consumes a scarce daily allowance (100/day). Those facts materially change an agent's decision to call it.

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 short sentences, front-loaded with the destructive action and scope, followed by consequence and quota. No filler or repetition of the title.

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?

Annotations already declare the destructive/open-world profile and the schema documents both params, so the description only needed consequence and quota context — which it supplies. A note on downstream effects (e.g. whether the thread also vanishes from unibox) would have closed the last gap.

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% and both parameters are documented there, including where chatId comes from (list_chats) and the connectionId fallback. The description adds nothing to parameter meaning beyond emphasizing a single chat, so baseline 3 applies.

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?

Specific verb 'Delete' plus precise resource and scope: 'ONE of your LinkedIn conversations from your inbox'. The 'ONE' emphasis separates it from bulk operations like bulk_delete_contacts, and 'conversation' separates it from delete_message.

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?

Gives a clear precondition ('confirm with the user first') and a quota constraint, which is strong operational context. It stops short of naming the sibling alternative (e.g. delete_message for a single message) for an agent that wants a narrower deletion.

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