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 nothing beyond that: no pagination behavior, no result ordering semantics beyond the filter list, no note on how price ranges or availability interact. It restates filters rather than disclosing behavior.

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?

One compact sentence with the verb and resource front-loaded and filters enumerated after. It wastes no words, though the trailing list of facets is dense rather than structured.

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 14-parameter search tool with 0% schema description coverage and a required gender parameter that the description never mentions, the definition is under-informed. It roughly covers half the parameters and gives no hint of the return shape or paging, even though an output schema exists to handle results.

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 there are 14 parameters, so the description must compensate. It names most filter concepts (category, designer, color, size, availability, price, sale, sort) but omits q, page, limit, attribute, and critically the required gender parameter, so a large share of parameters remain undocumented.

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 clear verb (Search) and resource (Moda Operandi products) and enumerates the filter facets, which distinguishes it from siblings like modaoperandi_product or modaoperandi_designers. It does not explicitly contrast itself against those siblings, but the search framing is unambiguous.

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?

There is no indication of when to use this tool versus modaoperandi_categories, modaoperandi_designers, or modaoperandi_product, nor any prerequisites or exclusions. The sentence only lists filters, leaving the agent to infer that this is the general product query entry point.

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