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

Annotations already flag destructiveHint=true and openWorldHint=true, yet the description adds real value beyond them: the deletion propagates to LinkedIn itself, it is irreversible, user confirmation is required, and there is a 100/day rate limit. These are exactly the behavioral facts an agent needs before invoking a destructive tool.

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?

Compact and mostly front-loaded, with the id-provenance prefix followed by the action and its consequences. The bracketed '[Ids out: none.]' notation is slightly noisy but does convey the absence of a return value efficiently.

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 two-parameter destructive tool with no output schema, the description covers everything material: required id source, account selection remains in the schema, irreversibility, confirmation requirement, rate limit, and confirmation that nothing is returned.

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 chatId and connectionId are already documented in the schema. The 'Ids in: chatId ... from list_chats → chats[].id' prefix reinforces the provenance but duplicates what the schema already says, so the baseline of 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?

States a specific verb and resource ('Delete ONE of your LinkedIn conversations from your inbox') with explicit scope ('ONE'). It is readily distinguishable from the sibling delete_message, which targets messages rather than whole conversations.

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 operational guidance ('confirm with the user first', daily allowance of 100 a day) but never states when to prefer this over alternatives like set_chat_status, delete_message, or simply leaving the chat alone. Usage context is implied rather than routed.

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