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

Annotations already declare the write/open-world/non-idempotent profile, and the description adds real value beyond them: MCP calls are free but rate-limited, the HTTP endpoint costs $0.10 USDC, an escrow is being created, and customer_support_code must be persisted. It does not describe reversibility of the escrow lock.

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 text is jumbled and poorly front-loaded: the actual purpose ('Create the escrow') appears third, pricing is split across two spots, and 'customer_support_code' is stated twice ('KEEP customer_support_code from the answer' and 'Persist customer_support_code'). The 'Identical to POST /air/intents' line is likely a copy-paste error that adds noise.

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?

With an output schema present, return values need not be explained. The description covers pricing model, sequencing, and key parameter handling, which is nearly complete for a financial intent tool. The only blemish is the misleading /air/intents reference for a train endpoint.

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 100%, so the schema fully documents all three parameters. The description reinforces that offer_id must be the quote's offer_id, but adds no syntax or format detail beyond what the schema already carries, matching the baseline for full schema coverage.

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 core purpose is stated with a specific verb and resource: 'Create the escrow for a quoted journey.' It also implies the train-specific scope through 'Next: brij_buy_train'. However, it never explicitly distinguishes itself from create_flight_intent / create_product_intent siblings, and it confusingly cites POST /air/intents for a train tool.

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 provides clear sequencing: use the offer_id from the quote and 'Next: brij_buy_train', which routes the agent through the workflow. It does not, however, state any when-not-to-use condition or the alternative siblings to pick instead.

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