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

Annotations already flag destructiveHint=true, but the description adds real value beyond them: the deletion is a soft delete, data is never hard-deleted, and an explicit user confirmation is required first. It stops short of explaining reversibility/restore behavior or what happens to related records.

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, with the soft-delete behavior and confirmation requirement front-loaded. Every clause carries information.

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 not be described, and annotations cover the destructive profile. The description supplies the soft-delete and confirmation context, but omits whether the archive is reversible and how it affects dependent data such as sessions or setups.

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 coverage is 0% for two parameters. The description conveys the semantics of 'confirmed' (explicit user confirmation required) but says nothing about 'vehicleId' or how the confirmation must be supplied, so it only partially compensates for the schema 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 (archive) and resource (connected user vehicle) and pins down the mechanism ('TuneWorks soft-delete behavior'), which distinguishes it from a hard-delete. It does not explicitly differentiate itself from the many sibling archive_* tools, so it falls short of a 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?

'Requires explicit user confirmation' gives one clear precondition for calling it, which is genuine usage guidance. However, it never says when to archive vs. update or otherwise deactivate a vehicle, nor names any alternative sibling, so the routing guidance is only implied.

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