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

Annotations declare destructiveHint=true, and the description adds substantial context beyond that: exactly which resources are frozen, which remain mutable (invitations, applicant review, labels, announcements, NDA bypass, ticket conversation), and that manager addition still works. It also discloses side effects like tester notifications being removed and managers being emailed, plus token single-use and expiry behavior.

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 description is front-loaded with the core action and effects before the freeze list and two-step instructions. The freeze/no-freeze enumeration is long but each item carries real behavioral information; only minor trimming would improve it.

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, two-step mutation with no output schema, the description covers consequences, invariants (cannot archive a finished beta), reversibility, the full confirmation workflow, and token lifetime. An agent has everything needed to call it safely and correctly.

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%, so both productId and confirmationToken are already documented in the schema. The description reinforces the two-step token workflow (omit first, resend with same arguments), but adds no syntax or format detail beyond what the schema provides, so the baseline 3 is appropriate.

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 and resource ('Archive this beta project') and immediately enumerates the concrete effects (notifications removed, managers emailed, screening form closed). It is clearly distinguished from siblings like pauseBeta and restoreBeta through the freeze/no-freeze breakdown.

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?

It states a hard precondition ('A finished beta cannot be archived'), names the reversal tool ('Reversible with restoreBeta'), and gives an explicit two-step invocation protocol with when to call with and without the token. Nothing about when to use this tool is left to inference.

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