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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful context beyond that: results are capped at the top three, ranking is simulated from a buyer agent's view, and the rank output is conditional on passing resource. It doesn't mention rate limits or caching, but for a read-only sampling tool that is a minor gap.

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?

Two tight sentences, front-loaded with the free-tier nature and the result shape, then the sibling comparison. Nothing is wasted or repeated from structured fields.

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?

Simple two-parameter read tool with full schema coverage and annotations that carry the safety profile; the description states the return shape (top three plus your rank) well enough that no output schema is needed. Nothing required for correct invocation is missing.

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, and the description goes beyond it by explaining the conditional effect of the optional resource parameter (“your rank if you pass resource”). That behavioral linkage isn't expressed in the schema's plain URL description.

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 concrete verb and resource: it returns the top three Bazaar results a buyer agent would see for a task, plus your own rank when resource is supplied. It also names the sibling rank_check and explains how that paid tool differs, so the agent can separate the two without opening either 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?

"Free" plus "the paid rank_check adds the signals where you trail the listings ahead of you" clearly implies when to reach for this tool versus the paid alternative. It doesn't spell out explicit exclusions or rate limits, but the free-vs-paid split is a usable routing cue.

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