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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is covered. The description adds meaningful nuance beyond them: the operation 'never hard-deletes data' (soft/reversible removal) and requires explicit confirmation, which explains why the `confirmed` flag exists. It doesn't state whether an archived session can be unarchived or whether the call is idempotent.

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 sentences, zero filler, action stated first and the two behavioral caveats front-loaded immediately after. Every clause 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?

An output schema exists, so return values need no explanation here. For a low-complexity, two-parameter mutation the description covers the safety profile and the confirmation gate adequately. Minor gaps remain around reversibility/unarchive behavior and sessionId sourcing, but nothing essential to calling it 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 0% for the two parameters. The sentence 'Requires explicit user confirmation' directly conveys the semantics of the `confirmed` flag, but `sessionId` is left entirely to the name — no indication of format, source (e.g., from list_sessions), or whether it accepts an archived session. Partial compensation for a real 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?

States a specific verb and resource: 'Archive a connected user driving session.' This clearly separates it from the parallel archive_* siblings (archive_vehicle, archive_setup, archive_maintenance) by resource, and from update_session/create_session/copy_session by action. It stops short of explicitly naming which sibling to prefer under which condition, so a 4 rather than 5.

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?

Provides one real usage constraint — that explicit user confirmation is required — which effectively tells the agent not to call this unprompted. However, it never contrasts this tool with update_session or explains when archiving is preferable to simply updating or leaving a session alone.

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