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

Annotations flag destructiveHint=true but cannot say what is destroyed; the description explicitly warns that 'an omitted description may be cleared', which is exactly the destructive mechanism an agent must know before calling. It also discloses the required-field constraint and the PUT (full-replace) semantics, adding real context beyond 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?

A single dense sentence, front-loaded with the WRITE classification and the most consequential semantic (the possible clearing of description), with the endpoint as a trailing reference. No wasted words.

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 mutation tool with no output schema, the description supplies the essential behavioral facts: write nature, required name, full-replace semantics, and the destructive description clearing. It stops short of naming the target list parameter explicitly or noting permission/idempotency implications, though idempotentHint already covers the latter.

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 0%, so the description must carry parameter meaning, and it does: name is required, description is optional and destructive when omitted. The list_id target is conveyed only indirectly via the PUT path template, leaving its role slightly implicit.

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?

The description names a specific verb+resource ('rename a list and/or change its description') and pins down scope with 'a full update', which separates it from sendlane_create_list and sendlane_get_list. An agent can identify the operation without opening the schema.

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?

Usage is implied by the 'WRITE' prefix and PUT semantics, which suggest updating an existing list, but no sibling is named and no when-not condition is given. Nothing tells the agent why to prefer this over create_list or get_list for a given intent.

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