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

With no annotations, the description carries full burden. It discloses rate limits (3/day/IP), the nature of the report (free tier), and what it checks (serviceName/tags/icon). It lists outputs clearly. No destructive behavior is implied, and no auth requirements are mentioned, which is acceptable for a read-only health report.

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 front-loaded with key details (free, rate limit) then expands on outputs. It uses a colon to list outputs, making it readable. Every sentence contributes value, though it could be slightly more concise without losing clarity.

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 is simple (2 optional params, no output schema) and the description covers inputs, outputs (including market rank among all Bazaar domains), usage details, and limitations. It is fully sufficient for an agent to decide when and how to invoke the 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 coverage is 100%, with both parameters (payTo, domain) described in the schema. The description reinforces that one of the two is needed ('Pass your merchant domain or payTo address'), but adds no new parameter details beyond the schema. Baseline 3 applies since schema does the heavy lifting.

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 provides a 'FREE x402 merchant listing health report' for a given domain or payTo address. It specifies the resource (merchant listing health) and action (check), listing outputs like serviceName checks, call counts, revenue proxy, market rank, and fix list. This distinguishes it from sibling tools like get_bazaar_category_trends or get_bazaar_competitors.

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 tells the agent to pass 'your merchant domain or payTo address' and mentions a rate limit of '3/day/IP'. It contextualizes the tool as 'The free tier of the paid trends/competitors/audit suite', implying when to use it (initial free check) and suggesting paid alternatives for deeper analysis. No explicit when-not to use, but clear context.

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