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 the interoperable-slug detail, but says nothing about result size, pagination, or coverage limits for a 'full directory' return.

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 front-loaded sentence with zero filler; the directory contents and the slug interoperability note are the only two facts and both earn their 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?

An output schema exists, so return values need not be explained, and the annotations cover safety. The gap is the undocumented required 'gender' parameter, which an agent must guess at to call the tool correctly.

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% and the single required 'gender' parameter is never mentioned in the description. The phrase 'a Farfetch department' hints that gender selects the department, but the valid values (e.g. men/women) are not documented anywhere, leaving a required input 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?

The description names a specific verb+resource ('full designer directory') and enumerates the returned fields (name, slug, URL), so the agent knows exactly what it retrieves. It only partially distinguishes itself from siblings, naming farfetch_search as a downstream consumer rather than contrasting with farfetch_categories.

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 supplies a concrete downstream workflow: 'each slug usable directly with farfetch_search's designer filter,' which tells the agent why to call this and how to chain it. It does not, however, state when to prefer this over farfetch_categories or farfetch_search directly.

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