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

With no annotations provided, the description carries the full burden and does substantial work: it discloses protocol adapter routing (MCP / A2A / HTTP-x402), spend-cap enforcement, dry-run default for x402 settlement, the signed receipt binding, and the fact that Clearhouse relays payment without seeing the private key. This gives the agent a clear model of side effects and safety behavior.

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 leads with a one-sentence summary, followed by a compact behavior block and a structured Args list. No sentence is filler — even the receipt-binding chain ('intent -> execution -> settlement -> outcome') concisely communicates the guarantee. It is long only because the tool is complex, and it front-loads the essential action.

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?

The tool has five parameters, no annotations, and an output schema (so return values do not need to be described). The description covers the full call flow, parameter semantics, optional behaviors, payment handling, and the receipt result, and it links to the sibling tools (search_agents, quote_call) that precede it. No critical information needed to select or invoke this tool correctly is missing.

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%, so the parameter explanations in the description are the only guidance available. Every one of the five parameters receives an added semantic: listing_id is tied to search_agents results, tool gains the omit-to-list behavior, args_json is a JSON object of tool arguments, caller_ref is identified as an opaque receipt identifier, and payment_json gets a precise JSON structure and signing source. This fully compensates for the schema gap.

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+resource: 'Call a listed remote service THROUGH Clearhouse and get a signed receipt.' The description further clarifies the role by mentioning protocol adapters, spend caps, and a signed receipt, which distinguishes it from siblings like search_agents (listing), quote_call (pricing/typed_data), and service_evidence (post-hoc verification).

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 description references the prerequisite flow — 'listing_id: id from search_agents results' and payment_json produced by signing quote_call's typed_data — which tells the agent when this tool fits in the workflow. It also gives an explicit usage note for the optional 'tool' parameter ('omit to list the service's tools'). However, it never states when-not-to-use or points to an alternative for a specific condition, so it falls short of an explicit routing rule.

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