browse_products

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

With no annotations, the description carries the behavioral burden. It discloses that the tool retrieves/reads data, supports pagination, and returns product details, but it does not explain how pagination is controlled given only a limit parameter, nor does it describe response format or failure behavior.

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 three concise sentences with no filler or repetition. It front-loads the core purpose, then adds pagination and parameter-specific behavior efficiently.

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 description is adequate for a simple browse/read tool, especially with fully described schema parameters. However, there is no output schema, and the description does not clarify pagination mechanics or response structure, leaving a noticeable gap for an agent trying to use all features effectively.

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?

The input schema covers all three parameters with descriptions, so the baseline is 3. The description adds minimal value: product_id is said to return detailed info for a single product, but limit and include_inventory are not meaningfully expanded beyond their schema descriptions.

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 retrieves a list of products and can optionally retrieve a single product by ID. This is a specific verb+resource combination that is distinct from siblings like browse_orders, browse_customers, and create_product.

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 implies usage: use it to browse products, and use product_id to get one product's detail. However, it does not explicitly differentiate from sibling tools such as list_inventory_items, which is relevant because inventory information is optional here but inventory-specific tools exist.

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