design_search_styles

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

No annotations are supplied, so the description carries the full behavioral burden; 'Search' weakly implies a read-only lookup, but nothing else is disclosed. It says nothing about how filters combine, whether an empty query returns everything or nothing, result ordering, or the default/max result count beyond what the schema's limit parameter states.

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 no filler; the verb and resource families come first. It is efficient, though at one sentence for a six-parameter search tool it is on the thin side rather than maximally 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 six-optional-parameter search with no annotations and no output schema, the description leaves key gaps: what a result actually contains (style names, ids, full records), what happens with no filters, and how this differs from design_suggest_style or design_get_style. It is adequate to start a call but not sufficient to call confidently within this dense style/symbol/recipe tool family.

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 100%, so the schema already documents all six parameters and the baseline of 3 applies. The description adds mild value by mapping the enumerated 'kind' values to concrete entity families (movement/artist/media), but never mentions the limit parameter or whether query and filters are ANDed or ORed.

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 (search) and the three resource families (art movements, artist profiles, media types) plus the searchable axes, which is far more than a restatement of the name. It does not, however, differentiate itself from nearby siblings such as design_suggest_style, design_get_style, or design_search_symbols, so an agent cannot tell purely from the description which style-lookup path to take.

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?

Listing 'by keyword, era, region, or tags' implies how to drive the tool, but there is no explicit when-to-use / when-not-to-use statement and no named alternative. An agent must infer that this is the browse-and-filter path while design_suggest_style is the recommendation path.

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