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

Annotations already declare readOnlyHint/openWorldHint, and the description adds real behavior: fixed page size of 20, offset pagination granularity, and that facets carry live per-option counts. It stops short of describing response shape, but an output schema exists so that is covered.

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?

Dense and front-loaded, opening with what one call returns before covering the pagination and facet mechanics. The facet example is wordy but functional; little is wasted.

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 paginated browse tool with an output schema and full schema coverage, the description supplies the pagination contract, sort options, category provenance, and facet feedback loop an agent needs to call it correctly. Nothing essential 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 coverage is 100%, so the baseline is 3, but the description genuinely enriches it: it explains where category paths come from, restricts offset to increments of 20, and gives a worked facet syntax example (benefit:bags,dotcomreportingcolour:black, one value per property).

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 specific verb and resource ('One page (20 products) of a Burberry category/browse listing') and can be told apart from siblings like burberry_product, burberry_search, and burberry_categories without opening a 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 concrete usage context: category comes from burberry_categories' own url field, offset advances in 20s, sort selects order, and facets are fed back from the same response. It never explicitly contrasts against burberry_search, so a 4 rather than 5.

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