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

Adds real context beyond the annotations: it names the external dependency ('Ask Fresh SEM'), constrains the payment to the exact official-USDC amount from the quoted wallet, and gives an important safety guarantee ('This never signs or broadcasts'). It does not explain the readOnlyHint=false implication (i.e., whether verifying advances or records order state), failure/timeout behavior, or rate limits.

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 zero filler; the action and its scope come first and the safety constraint is placed at the end where it reads as a guarantee rather than a caveat.

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 no output schema, the description carries the return-value burden and only says it returns 'the verified order state' without indicating possible outcomes (no payment found yet, mismatched wallet/amount, pending confirmation). For a verification tool an agent must react to before proceeding, that is a meaningful gap, though the safety and external-service context is present.

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% with only two params, so the schema already documents order_id and access_token fully; baseline 3 applies. The description adds the notion of the 'quoted sending wallet' but never ties it to a parameter, so it contributes no mapping beyond the schema.

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?

States a specific verb (look for / verify) and resource (the exact official-USDC payment for an order) plus the outcome (verified order state). It is distinguishable from submit_payment_proof (which submits) and create_quote (which originates the order), but it does not explicitly differentiate itself from the sibling get_order_status, which reads similarly.

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?

Usage is only implied through workflow vocabulary: 'the quoted sending wallet' points back to create_quote and the post-submission verification step. There is no explicit when-to-use statement, no exclusion of alternatives such as get_payment_requirements or get_order_status, and no stated prerequisites or ordering relative to submit_payment_proof.

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