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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds genuine value by specifying 'soft-delete', telling the agent the record is not permanently removed — but it omits whether the action is reversible/restorable, what happens to existing conversations or references, and any permission requirements.

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?

A single compact sentence with the key clarification parenthesized immediately after the verb. No filler, and the most important nuance (soft-delete) is front-loaded.

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 one-parameter tool with annotations covering destructiveness, the description covers the essentials of what happens. However, with no output schema and an undocumented parameter, an agent still lacks the ID semantics and any post-archive behavior (restorability, side effects) needed to invoke it confidently.

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 parameter assistantId is undocumented in both schema and description. The description gives no indication of format, source, or whether the ID is the assistant's unique identifier versus an external reference, so it fails to compensate for the coverage gap.

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 states a specific verb and resource ('Archive an assistant') and clarifies that archiving means soft-delete, which resolves the main ambiguity an agent would have. It does not differentiate from siblings (e.g., assistants_update), but the operation is distinct enough in the toolset and there is no competing archive/delete sibling to route against.

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?

There is no guidance on when to choose archive over assistants_update, nor any stated prerequisite or condition (e.g., when an assistant is obsolete vs. merely modified). The agent is left to infer usage entirely from the verb.

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