Search the creative library

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

No annotations provided, so description fully shoulders behavioral disclosure. It explains the AND-of-substrings search, query length/term limits, and advises inspecting preview metadata. Lacks explicit read-only statement but search behavior is clearly non-destructive.

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?

Description is well-structured with purpose first, then algorithm details, then usage hints. Every sentence adds value; slightly lengthy but all content 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?

Covers purpose, search behavior, interaction with two sibling tools, and parameter constraints. Lacks output format and error handling, but for a search tool without output schema this is acceptable given the guidance provided.

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 low (25%), but description adds crucial detail: query should be short single-word, max 80 chars, first 4 terms ANDed. Kind parameter enumeration is clear from context. Limit and offset are standard and not elaborated.

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 clearly states the tool searches curated creative library items (examples, templates, presets, shapes) and distinguishes itself from sibling 'find_matching_examples' by explicitly contrasting the search algorithm.

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?

Provides explicit guidance: use short single-word queries, prefer find_matching_examples for brief matching, and exclude recent slugs from plan_creative_video for fresh work.

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