search_assets

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

Discloses that returned previews are watermarked and can be used directly, and that the license page is for purchase. No annotations are provided, so the description carries the burden well, though it omits details like pagination or rate limits.

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 with no wasted words. First sentence establishes purpose and scope, second sentence details output and usage.

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?

Adequate for a search tool with moderate complexity. Describes return type and usage of results, but lacks details on response structure (e.g., fields in each result) and does not mention default limit or pagination. Could be more complete given no output schema.

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?

All parameters have schema descriptions, and the description provides a query example but adds no further semantic value beyond the schema. Baseline of 3 is appropriate given 100% schema coverage.

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?

Description clearly states it searches a royalty-free catalog with specific asset counts and types. It distinguishes the search action from siblings like get_asset or download_preview, but does not explicitly differentiate from get_categories.

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?

Implies usage for finding stock images/videos, but lacks explicit guidance on when to use this tool versus alternatives like get_asset or download_preview. No exclusions or prerequisites mentioned.

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