roboflow_search_images

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

With no annotations, the description carries the transparency burden. It discloses pagination limits (max 250), workspace fallback, and dry_run preview. The output schema exists, so return value details are not required. It does not mention ordering or other side effects, but covers key behavioral aspects.

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?

The description is extremely concise, using multiple sentences to front-load purpose and then detail filters, pagination, and dry_run. Each sentence adds value with no redundancy.

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 9 parameters (1 required) and no output schema needed, the description covers most parameters and behavioral aspects. It lacks guidance relative to sibling search-like tools (e.g., get_image), but is complete for the core functionality.

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 0% (no parameter descriptions), so the description must compensate. It explains most parameters: tag, class_name, prompt as filters; limit and offset for pagination; workspace fallback; dry_run. The 'fields' parameter is not explained, but overall adds significant value beyond 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 clearly states the tool searches images in a Roboflow project, specifying filtering by tag, class_name, or prompt. It distinguishes itself from sibling tools like roboflow_get_image (single image) and roboflow_list_image_batches (batches) by explicitly describing search and pagination.

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 explains filtering options and pagination, implying use for searching with specific criteria. However, it does not explicitly state when to use this tool versus alternatives like roboflow_get_image for a single image, or when not to use it.

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