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

With no annotations provided, the description carries the full behavioral burden and does so richly: verify_status enum values (verified/failed/unverified_verifier_down), httpStatus and contentMatch fields, a receipt with checked/verified/failed counts, the promise that bad results are flagged rather than dropped, and the settlement guarantee ('search is produced before settlement'). It also discloses the no-wallet property and unpaid-call behavior, which an agent must know before invoking.

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 core purpose and price are front-loaded in the first clause, and the dense single paragraph covers distinct concerns (payment, verification, status values, receipt, guarantee) without pure filler. It is information-heavy but could be more scannable as structured bullets, which keeps it below a 5.

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 must describe return values, and it does – enumerate the response shape via verify_status, httpStatus, contentMatch, and the receipt counts. Combined with the payment and failure semantics, an agent has everything needed to call and interpret the tool correctly.

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 both parameters (query, maxResults) are already documented in the schema, establishing the baseline of 3. The description adds semantic context around what results carry after verification but does not extend the parameter-level meaning (e.g., pagination or query syntax) 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?

The description opens with a specific verb+resource framed precisely: a 'web search where every result is independently checked by Flow.' It also names the sibling context indirectly by emphasizing the payment/verification model that distinguishes it from flow_health, flow_paycheck, and flow_quote. An agent can identify this as the paid, verified search endpoint without opening the schema.

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 gives clear invocation context – $0.01 USDC via x402 on Base, and that an unpaid call returns a payment challenge – plus a concrete path to use it ('any x402 client, or the @flowexecutor/flow-mcp stdio package'). However, it never states when to choose this tool versus an alternative search or versus the sibling payment tools, so usage is implied rather than guided.

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