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

Annotations already declare destructiveHint=true and readOnlyHint=false; the description adds value by naming the effect (pausing and hiding) and implicitly signaling reversibility through the unarchive option. It does not explain what happens to active leads/enrollments in the sequence or what permission is required, which matters for a destructive-flagged mutation.

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 short clauses, front-loaded with the action. There is mild redundancy between the title echo and the second clause, but no wasted sentences.

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?

Wrong — recomputing: with an output schema present, 100% schema coverage, and annotations covering the safety profile, only the side effects on enrolled leads and the relationship to update_sequence_status remain unexplained. That gap is modest but real for a destructive toggling tool.

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%, including the archived boolean's 'true to archive, false to unarchive' semantics and the workspace_id fallback, so the schema already carries the parameter meaning. The description adds nothing about how the archived toggle interacts with the described 'pause and hide' behavior, so 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 (archive/unarchive) and resource (sequence), and adds the effect ('pause and hide them'). The resource name alone distinguishes it from archive_list, archive_template, and archive_contact, so no further sibling disambiguation is strictly required.

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 only implied via 'to pause and hide them'. It never addresses when to use this versus pause-style siblings like update_sequence_status or unsubscribe_lead_from_sequence, nor does it state prerequisites such as needing the sequence not to be actively sending.

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