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

Annotations already declare read-only and open-world behavior, but the description adds important context: $0.01 USDC paid via x402 inside the call and failed calls are not charged. It also previews returned artifacts, including rank, competitor listings, and trailing signals.

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?

It front-loads the rank question and then compactly covers operation, outputs, free sample, price, and failure billing. The SEO/competitor sentence is slightly redundant, but the description remains efficient overall.

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 still explains what comes back and which signals are compared. The input schema and annotations cover parameters and safety, so an agent has enough information to select and call it 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 coverage is 100%, so task, resource, and network are already documented in the schema. The description reinforces 'your task' and 'your listed resource URL' but adds no syntax, format, or network-filter detail 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?

Names a specific operation: it runs the search a buyer agent would run and returns rank, competitor listings ahead, and trailing signals. The x402/Bazaar scope and the free sample endpoint separate it from generic analytics siblings.

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?

Implies use when checking Bazaar search rank, SEO, and competitor position, and gives a free sample endpoint plus per-call price as a decision aid. It does not explicitly state when not to use it or name sibling tools like rank_sample or lint_listing as alternatives.

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