ghost-x402-market-intel-vet-schema

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

With no annotations, the description carries the full burden, and it does an excellent job. It discloses the paid nature ('Paid per call via x402'), the two‑step process ('Omit it to receive the payment terms; call again with it to run the tool'), a free preflight endpoint with rate limit ('free preflight at /v1/commerce/search/preflight (3/day)'), and the return structure ('USE/WATCH/AVOID with the exact call, a fallback, valid_until and recheck_when'). This goes well beyond what a schema or annotations would typically provide.

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 is dense but every sentence serves a purpose. It is front-loaded with the core purpose and usage, then details the evidence and return structure, then the cost/preflight. It is not overly verbose, but a few sentences pack multiple ideas. The structure is logical and scannable, earning a 4.

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?

Despite lacking an output schema, the description explains the return format, the payment flow, the need for a payment signature, and the preflight option. It covers the main triggers for re‑consultation. It does not mention error handling or limits beyond the preflight, but for a tool of this complexity it is fairly complete. A 4 reflects that it covers the essential agent needs without exhaustive edge cases.

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 86%, so the baseline is 3. The description does not add extra meaning to the parameters beyond what the schema already specifies (e.g., network, capability, min_payers). It explains the ranking logic (independent payers, calls-per-payer, etc.) but that is not parameter semantics. No additional parameter-level guidance is given, so a 3 is appropriate.

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 clearly states the tool's job: 'Decide which x402 provider to pay'. It specifies the resource (x402 providers) and the action (decide/rank/return verdict). It distinguishes itself from siblings by describing a search-and-decision function, though it does not explicitly name alternatives. It is more specific than a tautology, earning a 4.

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 provides explicit conditions for when to use the tool: 'Consult when the provider is unknown, when a decision you hold has passed its valid_until, or when the price, health, verdict or funding of one materially changed.' It also advises when not to use it ('reuse a held decision until it expires or a trigger fires, rather than asking again'). However, it does not mention sibling tools as alternatives, so it lacks explicit exclusion guidance but still offers clear context.

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

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

With no annotations, the description carries the burden and it does disclose the key side effect: 'Paid per call via x402.' It also describes the signed receipt output. It does not detail the two-step omit-signature/call-again flow, but that is covered in the schema, so the description adds meaningful behavioral context without contradiction.

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?

Three sentences, front-loaded with the core question, and no wasted words. It packs scope, usage, output, and cost into a compact description.

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?

Given no output schema, the description does a good job by naming the verdict enum and signed receipt. Combined with the self-documenting schema, the agent has enough to decide when to call and roughly what will come back. A full response shape would make it a 5, but it is otherwise complete.

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 baseline is 3. The description adds thematic context (endpoint liveness, quote-vs-advertised price) that maps to endpoint_url and advertised_amount, but it does not add parameter-level detail beyond what the schema already provides.

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 action ('vetting' a seller before payment), names the exact context (unknown x402 seller, payment address already in hand), and lists what it checks. It also names the verdict outputs, which distinguishes it from sibling search/freshness tools.

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?

Gives clear usage context: 'Use when one named provider or payment address is already in hand and you need a verdict before you pay it.' This implies it is not for discovery, but it does not explicitly name alternatives or state when-not-to-use, so it stops short of a 5.

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

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 it discloses important operational facts: it is paid per call via x402, it is a 'pre-spend' recheck, and it returns a DSSE-signed receipt. It does not detail failure modes or side effects, but the read-only 'check' framing plus billing behavior is strong.

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 is compact and front-loaded, with the core question in the first sentence and the usage trigger and billing behavior in the following sentences. Every sentence earns its place and there is no redundant filler.

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?

It covers purpose, usage, and payment behavior well, but there is no output schema and the description never explains what the response contains, such as whether it returns a new fingerprint, a changed/unchanged indicator, or the signed receipt. That is a meaningful gap for an agent invoking a paid tool.

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 the schema already documents url, known_fingerprint, and payment_signature. The description adds contextual flavor about a held fingerprint and payment, but does not materially go beyond the parameter descriptions already present.

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 clearly identifies a specific resource ('published JSON Schema or OpenAPI document') and a specific operation ('changed since a fingerprint you hold'), so an agent can tell this is a freshness/recheck tool. It does not explicitly differentiate itself from the sibling tools, but their names and this tool's schema-focused wording make confusion unlikely.

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 an explicit trigger: run when a provider's published contract may have moved before paying again. It does not list exclusions or alternatives, but the stated usage context is clear enough to guide selection.

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