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

With annotations already declaring readOnlyHint, idempotentHint, and destructiveHint false, the description adds useful behavioral context: it independently verifies Stripe payment and keeps research human-review controlled. There is no contradiction with the read-only 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 short sentences carry the operation, the payment verification condition, and the human-review constraint without repetition or boilerplate. The most important information is front-loaded.

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 simple read-only status tool, the core purpose and a key behavioral constraint are present, and the annotations cover safety characteristics. However, parameter semantics, possible status values, and return format are omitted even though there is no output schema to fill 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?

Schema description coverage is 0%, and the description never explains lead_key, how to obtain it, or its relationship to the order/checkout session. The parameter name and length constraints are present in the schema, but the description does not compensate for the missing semantic meaning.

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 names a specific action ('Read') on a specific resource ('commercial request state') and adds a distinct capability ('independently verify Stripe payment'). This clearly separates the tool from get_faie_offers and prepare_faie_checkout, though it does not explicitly mention 'mission queue status' or name the sibling alternatives.

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?

The phrase 'when a checkout session exists' gives a conditional context for the payment-verification behavior, and 'Research remains human-review controlled' implies a state nuance. However, the description never states when to choose this tool over get_faie_offers or prepare_faie_checkout, so usage must be inferred.

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