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

Annotations already flag destructive, idempotent, non-read-only, open-world. The description adds substantive detail beyond them: it may close admission and release a wallet hold, which tells the agent money and admission state are at stake. It does not explain the role of approval_receipt or how reconciliation resolves the uncertain state, keeping it from a 5.

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 with no filler, and the mutation warning is front-loaded at the end of the first sentence. The opening clause is vague, but nothing is redundant.

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 explained. However, for a destructive, idempotent, nested-parameter mutation with zero schema description coverage, the description is too thin: it leaves approval_receipt, quote_id, and idempotency semantics unaddressed.

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% across 5 parameters including a deep nested request object, so the description carries the full burden. It names "request, reservation and key" (mapping loosely to request, reservation_id, idempotency_key) but adds no meaning about their provenance or format, and omits quote_id and approval_receipt entirely.

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 gives a verb ("Reconcile") and an implied resource ("uncertain acceptance"), but the phrasing is abstract and never names the object being reconciled in tool-level terms. It does not distinguish itself from siblings like submit_cloud_motion, cancel_cloud_motion, or get_cloud_motion_status, so an agent must infer where this fits.

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?

"Reconcile uncertain acceptance" implies the use case: an agent whose earlier admission outcome is unknown. But it never explicitly says when to choose this over get_cloud_motion_status, get_cloud_motion_receipt, or re-submitting, and no prerequisites or exclusions are given.

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