browse_bundles

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

With no annotations provided, the description carries the full burden. It indicates a read-only 'browse' operation and adds context about curation and discount pricing, but it does not disclose details about the response format, ordering, pagination, or any potential side effects. For a zero-parameter read tool, this is adequate but not rich.

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 two sentences, front-loaded with the core action ('Browse curated product bundles'), and the second sentence adds valuable context about the bundles' value proposition. Every word earns its place.

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 complete enough for a simple, zero-parameter browse tool. It specifies the resource (bundles), the location (The Bag Kenya), and the key differentiator (discounted multi-item sets). While it doesn't detail return fields or ordering, such details are not essential for a straightforward browsing action.

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 tool has zero parameters and the schema coverage is 100%, so the description need not explain parameters. Per the rubric, zero parameters gets a baseline of 4. The description adds no parameter information, which is appropriate.

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 identifies the tool's function: 'Browse curated product bundles' with a specific resource (bundles) and context (at The Bag Kenya). It distinguishes itself from sibling tools like browse_products by focusing on bundles, which are a distinct product category.

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 when customers want discounted multi-item offerings, but it does not explicitly state when to use this tool over alternatives like browse_products or search_products. No exclusions or alternative recommendations are provided.

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