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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds real behavioral context beyond that — fixed page size of 20, offsets in increments of 20, and that facets come with live per-option result counts — though it omits rate limits or auth requirements.

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 the page-size and resource, then the parameter guidance. It is a single dense paragraph that borders on run-on around the facet explanation, but every sentence carries information an agent needs.

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?

For a 4-param browse tool with an output schema present (so return values need no explanation), the description covers category sourcing, pagination, sorting, and the facet feedback loop. Nothing essential to a correct call 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?

With 0% schema coverage the description carries the full burden and mostly delivers: category origin, offset increment, and a worked facets example ('benefit:bags,dotcomreportingcolour:black'). Only sort is weakly explained ('selects the result order') without listing allowed values, leaving one gap.

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 concrete verb and resource: returns 'One page (20 products) of a Burberry category/browse listing.' This clearly separates it from burberry_categories (the path source), burberry_product (single item), and burberry_search (keyword search). An agent can pick it 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 clear context for how to use it: category comes from burberry_categories' url field, and facet selections are fed back via the facets param. It does not explicitly state when to prefer burberry_search over this browse tool, so it stops short of full when/when-not guidance.

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