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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description goes further by disclosing the exact dimensions of the result set (price, commercial-use permission, credit requirements, in-app shipping, bot fetching, rules, connection methods). That is meaningful behavioral context beyond the annotations, though it says nothing about result limits or pagination.

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?

It is a single dense sentence front-loading a very long enumeration of asset types before getting to what results actually contain. The content is informative and not padded, but the run-on structure and lack of a leading verb make it harder to scan than it needs to be.

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?

With no output schema, the description correctly compensates by enumerating the fields each result carries (price, license, credit, shipping/bot rules, connection method), which is what an agent needs to judge relevance. It is nearly complete, missing only result-count or pagination behavior.

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 all four parameters (query, style, category, free_commercial_only) are already documented in the schema. The description echoes the category domain but adds no syntax, matching behavior, or combination semantics, so baseline 3 applies.

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 identifies the resource domain precisely (sources of UI kits, fonts, icons, illustrations, stock media, 3D) and what each result covers (price, license terms, credit, connection method). It distinguishes itself from the sibling get_asset, which returns 'the full card with the license quotes'. It never states an explicit verb like 'search' or 'find', so the action must be inferred from the tool name.

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 only routing guidance is the closing pointer to get_asset for the full license card, which implies this tool returns summaries. There is no statement of when to prefer it over find_tools, find_apis, or get_asset beyond that single hint, and no exclusion criteria.

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