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

Annotations already signal destructive and non-read-only behavior; the description adds that the submission is immutable, consumes a prior approval, and resolves the target only from stored data. It doesn't detail exactly what destruction occurs, but that is adequately implied by 'consume' and the destructiveHint annotation.

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 tight sentences, front-loaded with the action and prerequisite. No filler; each clause adds a meaningful constraint or behavioral detail.

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 three-required-parameter mutation with no output schema, the description plus annotations cover the prerequisite, target derivation, immutability, and queue destination. The only notable omission is explicit idempotencyKey guidance, but the parameter name and idempotentHint annotation mitigate that gap.

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?

At only 33% schema description coverage, the description partially compensates: 'recent human approval' tells agents assessmentId must refer to an approved assessment, and 'target resolved only from stored verified asset' explains why no target parameter should be supplied. However, idempotencyKey semantics are left entirely to the parameter name and annotation, so the description does not fully carry the parameter-documentation burden.

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?

Description uses specific verbs ('consume', 'submit') and identifies the resource ('assessment', 'managed queue') and condition ('approved', 'recent human approval'). It distinguishes launch_assessment from prepare/cancel/get/list siblings by emphasizing immutable final submission.

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 establishes when to use: after a recent human approval, and clarifies no target parameter should be used because the target comes from the stored verified asset. It doesn't explicitly name siblings like prepare_assessment or cancel_assessment as alternatives, so it stops short of full routing guidance.

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