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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the description correctly spends its words elsewhere: it discloses the return shape (LC codes, page links, cover images) and the ranking behavior (best matches first, brand examples first). That ordering note is real behavioral information not present in any structured field.

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?

Two sentences, front-loaded with the search capability, with the alternative-route sentence at the end where it belongs. The motif enumeration (butterflies, stingrays, birds, droplets...) is somewhat decorative but does teach the expected vocabulary.

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?

No output schema exists, so the description carries the burden of explaining return values and ranking — and it does so. All four parameters are covered by schema text, and the agent knows what it gets back and in what order.

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 adds genuine value by clarifying the 'and/or' combinatorics between motif and product type and by emphasizing that motif works across any of the eight site languages. Those are semantic additions beyond the enum and per-parameter text.

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 (find Vargov®Design compositions) plus the two search axes (element motif and/or product type). It explicitly names the sibling get_composition as the alternative for a different need, so an agent can route without opening either 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?

Clear usage context: use this for discovery, use get_composition for facts about one composition. There are no exclusions against the other siblings (ask_brand, configurator_link), but the primary fork is spelled out explicitly.

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