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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description still adds real value: permanence, that contacts/links/history are preserved, that a preview confirmation showing list name and contact count is required, and the not_found behavior for out-of-workspace ids. It omits the response shape and any permission requirements, keeping it below a 5.

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?

Four short sentences, front-loaded with the action and its permanence, then the non-obvious side effects and the confirmation/error behavior. Nothing is repeated and every sentence carries distinct information.

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, no-output-schema tool with fully documented parameters and rich annotations, the description covers consequences, confirmation requirements, and a known error case. It could still say what the success response contains, but an agent has enough to invoke 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 baseline is 3; the description goes slightly beyond by explaining that the confirmation is a preview the person sees with the list's name and contact count, which gives meaning to the confirm/confirmationToken/alwaysAllow trio. It adds no format or fallback guidance for listId beyond what the schema's pattern already says.

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 ("Deletes a contact list permanently") and clarifies that member contacts and their links/history survive, which separates it from destructive contact operations. It never names a sibling tool (e.g. lnkdrp_remove_contact_list_members or lnkdrp_delete_contact), so differentiation is inferred rather than explicit.

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 use case (permanently removing a list) is implied by the verb and the confirmation flow described, but there is no explicit when-to-use/when-not guidance or pointer to alternatives such as unarchiving, editing, or removing members only. An agent must infer which tool to pick from the name alone.

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