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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the description's job is the extra context, and it delivers: deleting a list does not destroy places, it relocates them, and each op result carries list_id and kind. The key consequence an agent needs before a destructive batch call is present. It does not mention the 20-op batch cap or conflict behavior, and the clause 'moves its places to Unscheduled or to.' is garbled and partially loses its meaning.

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?

Three sentences, front-loaded with the operation set, which is good structure. However the third sentence's truncated fragment ('or to.') is a defect that costs space without conveying meaning and forces the reader to guess the destination rule.

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, batched mutation tool with no output schema, the description covers the two most important behaviors (delete relocates places, results return list_id and kind). It is still thin on the batch limit, optimistic-concurrency expectations, and addressing (map_id vs draft_handle for unsaved maps), which matter when composing a call.

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 40% across five parameters, so the description should carry more weight than it does. It clarifies the ops payload semantics and adds the plan-list date-in-name convention, but says nothing about map_id, draft_handle, conversation_id, or expected_version, leaving that to the schema's own descriptions.

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 opens with a specific verb triad and resource ('Create, update ... or delete lists') and enumerates the update sub-cases (rename, change kind, pin to a plan list), so an agent can tell this is the list-lifecycle tool rather than the sibling map_edit_places. It stops short of naming the sibling it is distinguished from, so it lands at 4 rather than 5.

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 operation enumeration and the plan-list naming convention, but there is no explicit 'use this when / use X instead' guidance against map_edit_places or map_create. The one real selection rule (saved vs plan lists) lives in the schema's kind description, not the tool description.

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