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

Annotations only cover readOnly/idempotent/openWorld; the description adds the real operational context: auth headers (X-API-Key / Bearer), x402 settle-after-402 dual auth, and the warning that pricing is dynamic and must be read from PAYMENT-REQUIRED / meta.billing.price_usd_live rather than hard-coded. Missing rate-limit or failure-mode notes, so not a full 5.

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?

Front-loaded and dense, but the tail is a run-on mixing auth, a signup URL, and a note about dynamic pricing on meteora_brief — a different tool — which dilutes the sentence for this tool. Useful material, poorly scoped to the tool being described.

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?

There is no output schema, so the description should carry the return shape; it names the agentshare.price.v1 listings envelope and one billing field but never describes the listings returned or how best_offer's single pick is presented. Adequate for auth and mode selection, thin on results.

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% and the enum/default/description for mode, limit, currency and max_price_usd are already documented in the schema. The description's mode and budget guidance largely restates schema text and does not resolve the name/unit mismatch on max_price_usd (named _usd but described as being in VND or USD).

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?

Specific verb (quote) plus resource (commerce listings) and the mechanism (wraps search or best_offer into the agentshare.price.v1 envelope). An agent can distinguish it from search_listing / best_offer_under_budget as a wrapper layer, though the 'ACP/Virtuals-friendly' framing assumes jargon the agent may not share.

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?

Explicit routing by mode: mode=search for multiple listings, mode=best_offer for a single cheapest pick, max_price_usd with mode=best_offer for budget-constrained buyers. It does not say when to call this wrapper instead of the sibling best_offer or best_offer_under_budget directly, which is the main ambiguity left.

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