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

With no annotations provided, the description carries the full burden and it discloses the payment requirement, the two-step x402 flow, and the fact that results are icon ids rather than SVGs themselves. It does not mention rate limits or failure modes, but the core behavioral trait (paid, terms-based access) is clearly disclosed.

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 sentences deliver the core purpose, result format, and payment workflow with zero filler. The payment steps are compressed into a single clear sentence, and every sentence earns its 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?

Given no output schema, the description adequately explains the return type (matches with ids) and how to fetch render-ready SVGs. The payment workflow is also specified, so an agent understands the full sequence. It could mention error cases or pagination, but for this scope it is sufficiently complete.

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 provides 100% parameter coverage with examples, enums, and defaults for all five parameters. The description adds meaningful context for 'q' (semantic search) and 'x_payment' (the exact flow), but does not deeply elaborate on set/style/limit beyond what the schema states. The baseline of 3 is appropriate because the schema does the heavy lifting.

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 opens with a specific verb and resource: 'Semantic search across 12,900+ open-licensed icons', clearly distinguishing it from sibling tools like image_to_text or screenshot_url. It also states what is returned (matches with ids for SVG fetching), leaving no ambiguity about the tool's core function.

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?

The description provides clear context on how to use the paid aspect: call without x_payment to receive terms, sign them, then call again. It also points to the 'pricing' tool as a free alternative for listing all prices. However, it does not explicitly compare against sibling search or data tools, though the icon-specific scope makes usage obvious.

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