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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: it enumerates the normalized return fields (name, brand, price, image, availability) and notes the upstream page count, telling the agent what to expect from a call.

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?

A single dense sentence that front-loads the verb and resource, then the filters, then the return shape. No filler, though the packed clause structure makes the requirement statement slightly hard to parse.

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?

An output schema exists, so return-value detail is not strictly required, yet the description's 'at least one required' claim conflicts with the schema's single required field (gender). With 4 undocumented params and no enum hints, the agent lacks confirmation on pagination and how gender values are formed.

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 description coverage is 0%, so the description must carry the burden. It maps gender to 'department' and covers designer/category as filters, which is helpful, but it never explains the 'page' parameter's role or acceptable values. Notably, it claims designer/category are 'at least one required' while the schema only requires gender — a mismatch that leaves the true required combination ambiguous.

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 (browse) and resource (Farfetch's luxury multi-brand marketplace) plus the filter dimensions (department, designer, category). This clearly distinguishes it from sibling farfetch_product (single-item detail) and farfetch_categories/farfetch_designers (taxonomy lookups), though it never names those siblings explicitly.

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 'designer and/or category filter (at least one required)' note gives a usage constraint, so the agent knows a filter must accompany the department. However there is no explicit when-to-use-vs-farfetch_product guidance and no clarification that this is the listing/browse entry point versus the detail tools.

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