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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description still adds real operational context—required auth headers, x402 settlement after HTTP 402, and the fact that price is dynamically quoted rather than fixed. The 'never hard-code' pricing warning is a genuine behavioral trait. It loses a point only because the pricing detail drifts toward a different tool (meteora_brief) rather than this tool's own response 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?

Purpose and usage are well front-loaded, but the tail is padded with material unrelated to selecting this tool: a signup URL, a pricing-page link, and a dynamic-pricing paragraph about meteora_brief's $0.01–$0.30 range and PAYMENT-REQUIRED headers. That is a large fraction of the text that does not help an agent decide or invoke this two-parameter tool.

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?

For a two-parameter, read-only, open-world lookup with no output schema and full annotation coverage, the description supplies what is otherwise missing: when to use it, the cap semantics, and the auth/payment prerequisites that would cause a call to fail. Only the omission of the shape of the returned offer list keeps it from a 5.

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 both parameters are documented in the schema itself, including the exclusiveMinimum on max_price. The description's note to pass max_price 'in the same numeric unit the deployed API expects' restates the schema's 'same numeric scale as the API's pricing fields' with only a pointer to docs, adding minimal new meaning. Baseline 3 applies.

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 and resource ('Find the best offer for a product query') plus the defining constraint ('maximum price ceiling'), which is exactly what separates it from the sibling best_offer and search_products. An agent can identify the tool's job without reading 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 explicit trigger phrases ('under $X', 'below …', 'no more than …') for when to use it, and an explicit exclusion plus named alternatives ('Do not use for open-ended comparison without a cap—use search_products or best_offer'). This is the full when/when-not/alternative triad.

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