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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the description's 'Idempotent' is redundant. However, it adds real value by disclosing what does NOT happen (no curator follow, email, or payment) and that it captures 'new picks', which is side-effect 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?

The key fact (older name for save_list, saves to Library) is front-loaded, and each clause carries information. The phrasing 'Older name for save_list on a live free list' is slightly dense but still earns its place.

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 no output schema, the description usefully tells the agent to read back via saved_lists, and side effects are covered. But the undocumented required 'list' parameter leaves a real functional gap for a mutation tool, so it is only minimally complete.

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% and the single required 'list' parameter is undocumented in both schema and description. The description never clarifies whether 'list' is an ID, slug, or name, so it fails to compensate for the coverage gap on the one parameter the agent must supply.

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 the specific operation (saves a live free list to the Library with its new picks) and explicitly identifies it as the older name for save_list, which differentiates it from that sibling. The name 'get_list_updates' is misleading on its own, but the description plus title clarify that it is actually a save operation.

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?

'Only when asked' gives an explicit usage condition, and 'Read back with saved_lists' routes the agent to the correct sibling for verification. It implies save_list is the preferred modern name without stating outright to prefer it, which is a minor gap.

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