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

With no annotations, the description carries the full behavioral burden and does most of it: pagination semantics (pass next_offset back), price disambiguation (price is the exact USDC wallet charge; listPrice is the brand-store price/currency), and an explicit boundary about what is not returned here (on-chain minted count lives in get_drop_details). It does not mention auth/permission requirements or rate limits, which is the only remaining 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?

Front-loaded with a category tag and the core action, then ordered by decision relevance: when to use, when not to, return shape, next step. It is long-ish but every sentence carries distinct information with no restatement of the title.

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?

No output schema exists, and the description compensates fully by enumerating the page envelope ({limit, offset, total_count, has_more, next_offset, listings}) and the per-listing fields. Combined with the explicit alternative tool, prerequisite-free read semantics, and next-step routing, an agent has everything needed to call and continue 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 the baseline is 3, but the description adds operational meaning the schema lacks: why limit/offset matter (catalogue has thousands of items), and how the returned next_offset must be fed back into offset. It does not add format or syntax detail for brand_slug beyond the schema, which keeps it out of 5 territory.

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 specific verb and resource ('List active RRG listings, paginated, optionally scoped by brand_slug') and the [BROWSE] tag signals its class. It explicitly distinguishes itself from the nearest sibling by routing product-name/SKU/keyword lookups to search_products instead. An agent can tell what this does and what it does not do without opening 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?

Gives an explicit use condition ('when exploring the catalogue without a specific item in mind'), an explicit anti-condition with a named alternative ('If you already have a product name, SKU, brand, or descriptive keyword, call search_products FIRST'), and a reason (cost of paging thousands of items). It also names the follow-up path (get_drop_details + initiate_agent_purchase).

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