Browse a Woolworths category

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

Beyond the readOnlyHint and openWorldHint annotations, the description explains single-page returns, the need to read 'coverage' before making existence or best/cheapest claims, and the pagination termination rule. It also discloses location-dependent prices and availability, which is valuable behavioral context not present in the annotations.

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?

Four compact, front-loaded sentences carry the purpose first, then essential operational caveats. Every sentence adds information needed for correct invocation, with no filler or repetition of schema content.

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?

With no output schema, the description explains the most important output-related behaviors: one page at a time, a coverage field, and how to detect the final page. It could say more about the exact product fields returned, but the operational guidance is sufficient for the main use cases described.

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. The description adds value by clarifying the dependency between department, aisle, and shelf slugs, and by tying prices/availability to the current delivery location. It does not need to restate the schema's already detailed parameter 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 states a specific verb and resource: 'List the products in a department, aisle or shelf', and further clarifies that slugs come from list_categories. This cleanly distinguishes browse_category from search_products and get_product without opening any schemas.

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 guidance on when to use the tool: after list_categories, with the caveat that narrower levels require wider slugs. It also points to get_location/set_location for location-dependent pricing. It does not explicitly state when to prefer search_products over browse_category, so it stops short of a 5.

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