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

Annotations already declare destructiveHint=true and readOnlyHint=false, so safety framing is partly covered. The description adds genuinely useful context the annotations lack: the operation is bidirectional (archive/unarchive) and its effect is a visibility change rather than deletion, which softens the scary 'destructive' flag. It does not mention permissions or confirmation requirements, keeping it below a 5.

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 tight clauses with the action front-loaded and the effect immediately after. Slight redundancy between the title echo and the 'Archive lists to...' clause, but no wasted padding.

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?

An output schema exists, annotations cover the safety profile, and all three parameters are fully described in-schema, including the default and workspace fallback. Nothing an agent needs to invoke this correctly is missing.

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% — id, the archived boolean with its default, and workspace_id fallback behavior are all fully documented in the schema. The description adds no parameter-level detail beyond that, so the baseline 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 pair and resource ('Archive or Unarchive a List') plus the effect ('remove them from active views'), which is far more informative than the title alone. It is distinguishable from update_list or delete-style siblings by name, though it never explicitly contrasts with them.

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?

The phrase 'to remove them from active views' implies when to archive (to hide rather than delete), so usage is inferable. However, there is no explicit when-not guidance and no pointer to the sibling that should be used for other list changes (e.g., update_list for renaming).

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