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

With no annotations provided, the description must carry behavioral context. It clearly states this is a finalizing action (generates invoice) and implies irreversibility by calling it the final step. It also warns against premature invocation. However, it doesn't mention what happens if it's called with isServiceFlight=true (no invoice), which is a schema detail but still behavioral. Overall, it provides solid context for a mutating action.

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 extremely concise—just two sentences. It front-loads the critical flag ('FINAL STEP') and the prerequisite, making it unmissable. Every word serves a purpose, and the capitalized labels draw immediate attention without cluttering.

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 finalizing tool with explicit prerequisites and a schema that fully documents parameters, this description is complete. An agent knows exactly when to call it and what it accomplishes. There's no output schema, and none is needed to justify the invocation. The emphasis on prerequisites is essential context.

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 100%, so all 8 parameters are already documented in the schema. The description adds nothing specific about parameter meanings beyond that, which is acceptable given the schema's completeness. The baseline of 3 applies.

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 states 'Finalize the settlement and generate the invoice' with a specific verb and clear outcome. It distinguishes itself as the final step after preview_settlement, and the naming convention plus the 'FINAL STEP' label make its role unambiguous.

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 lays out the prerequisite: must have called 'preview_settlement' and received explicit confirmation from the pilot. The 'CRITICAL' warning reinforces when NOT to call it. This is actionable and leaves no ambiguity about the required preceding action.

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