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

No annotations are provided, so the description carries the behavioral disclosure burden. It adds useful behavioral facts beyond the schema: the 20-slot cap, English/Persian input support, and the dependence on an overall task for disambiguation. It does not explicitly confirm there are no side effects, but the described behavior is a read-only recommendation and nothing hints at mutation.

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?

Three compact sentences, each earning its place: core capability, one usage hint, and routing to the appropriate alternative. No repetition of schema or title.

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?

Given five parameters, no annotations, and no output schema, the description plus input schema cover the main operational contours: inputs, modes, styles, and batch limits. Minor edge behaviors such as what happens when a slot has no match or the list exceeds 20 are not addressed, but the core is adequately specified.

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?

The schema already documents most parameters (80% coverage), so the baseline is 3. The description adds value by explaining the 20-slot batch limit, bilingual slot names, and the instruction to provide task context so ambiguous slots resolve correctly—details absent from the schema.

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 action ('Pick a coherent Digche icon set'), a precise target ('up to 20 named UI slots'), and a distinguishing batch property ('in one call'). This clearly separates it from single-icon sibling tools like search_icons or get_icon_svg.

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 explicitly tells the agent when to prefer this tool: 'Use this instead of one search per icon when laying out a screen.' It also gives a concrete precondition for better results: 'Give the overall task so ambiguous slot names resolve correctly.'

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