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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known; the description adds the archive-routing note, which is useful context. However, it never mentions that several parameters (verification, archive_risky, archive_invalid) are irreversible or that contacts may be permanently deleted by the duplicate_removal flags — that disclosure exists only in the schema property descriptions. The phrase "Archiving is handled by archive_list" is also mildly ambiguous next to the archive_risky/archive_invalid params, though it refers to the list itself and therefore does not contradict the annotations.

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?

Two short sentences, zero padding, with the disambiguation front-loaded after the verb. The first clause restates the tool name/title redundantly, which is the only waste.

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?

With an output schema and full annotation coverage present, the description doesn't need to explain return values or safety hints. But for an 11-parameter mutation tool that can irreversibly archive emails and strip contacts from lists, the description is thin: it doesn't summarize the scope of changes or warn that omitted fields are left untouched, leaving the agent to reconstruct intent entirely from the schema.

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 all 11 parameters, including the required id and the irreversible booleans, are already documented in the schema. The description adds no parameter-level meaning (no examples, no interaction rules between duplicate_removal_* flags, no folder constraints), 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 ("Update a List - Update list properties") and explicitly carves out archiving as a separate operation performed by archive_list. The second half is somewhat tautological with the title, and it doesn't indicate which properties are updatable, but an agent can distinguish it from archive_list and from create_list.

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?

One explicit exclusion is given ("Archiving is handled by archive_list"), which routes the agent correctly for that one case. Beyond that there is no guidance on when to call update_list versus update_workspace, move_lead, or other mutations, and no prerequisites or side-effect warnings are stated, so most usage must be inferred from the name and schema.

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