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

Annotations already signal that this is a mutable, potentially destructive, idempotent operation. The description adds meaningful behavioral context by stating that it updates the private packet and CRM, does not issue shares or process payments, and should be confirmed only once, which goes beyond what the annotations alone convey.

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?

The description is two sentences long, front-loads the governing precondition, and provides key behavioral boundaries without wasted words. 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?

The description covers the core purpose, preconditions, and side effects, and an output schema exists so return values need not be explained. However, it omits guidance on the critical safety parameters (expected_version, confirmation_token, idempotency_key) that a destructive finalization tool should clarify for correct invocation.

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 description does not explain any of the five parameters, including the critical expected_version, confirmation_token, or idempotency_key. Because the description carries the burden when schema coverage is low but provides no parameter semantics, this is a meaningful 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 uses a specific verb ('Confirm') with a clear resource ('one closing') and states it is the finalization step for an evidenced SAFE closing. It distinguishes itself from workflow siblings by listing preconditions and side effects, so an agent knows exactly what this tool accomplishes.

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 explicitly states when to use the tool: 'only after signatures, approval, matching receipts, reconciliation and source gates pass.' It also gives when-not guidance by noting it does no share issuance or payment processing and should be used only once, which helps agents avoid misuse.

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