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

Annotations already disclose readOnlyHint=false, destructiveHint=true, and openWorldHint=false, so the mutation/safety profile is covered. The description adds only the vague scoping phrase 'in the active setup' and says nothing about whether this is a partial patch, what happens to omitted fields, or whether the destructive flag applies to the list contents rather than the list record itself.

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?

A single front-loaded sentence with no filler. It is appropriately sized but arguably too terse given the complexity of the operation it covers.

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 5 parameters, a nested object, 20% schema coverage, and no output schema, this description is far too thin. It omits update semantics, parameter meanings, and any behavioral detail beyond what the annotations already supply.

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 only 20% across 5 parameters, including a nested messageTemplate object with an enum and three sub-fields. The description lists no parameters and therefore does not compensate for the coverage gap, leaving messageTemplate, color, description, and name semantics undocumented.

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 an existing LinkedNav contact list) and scopes it to the active setup, which distinguishes it from update_contact and update_campaign. It never names or contrasts a sibling, but the resource noun is unambiguous enough for an agent to select it.

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?

No when-to-use, when-not-to-use, or prerequisite information is provided. The agent gets no guidance on how this relates to create_list, delete_list, or link_list_to_campaign, all of which operate on the same resource.

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