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 genuine behavioral detail beyond that: the fixed page size of 24, 1-indexed paging, and that pages beyond the last return an empty list rather than erroring. It doesn't cover rate limits or auth, which keeps it short of a 5.

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 clauses: the core behavior first, then the sibling routing. No filler, and the most decision-relevant information (what it returns) is front-loaded.

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?

An output schema exists, so return values need not be described. Both parameters, the paging boundary condition, and sibling alternatives are covered, and annotations carry the safety profile. Nothing needed 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 description coverage is 100%, and the schema already documents q as free-text keywords and page as 1-indexed defaulting to 1 with up to 24 items per page. The description largely restates this (page starts at 1, 24 items), adding little beyond the schema, so the baseline of 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 states a specific verb (Fetch), resource (Best Buy product listing items), scope (one page of up to 24, matching free-text q), and explicitly disambiguates from siblings bestbuy_product, bestbuy_category, and bestbuy_brands. An agent can select this tool without opening any 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 routing rules: use this for free-text product search, bestbuy_product for one SKU, bestbuy_category for department browsing, bestbuy_brands for brand browsing. Both when-to-use and named alternatives are covered.

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