List Kavel AI photo/video tools

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

With no annotations, the description carries the full burden. It discloses that each result includes a direct URL on www.kavel.ai, which is useful return information, but omits whether the operation is read-only, requires authentication, or has pagination 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?

The description is three tight sentences, front-loading the core purpose and followed by query usage and return details. Every sentence earns its place 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 the simple two-parameter list tool with no output schema, the description adequately covers purpose, query usage, and the key return value (direct URL). It could be more complete by noting read-only nature or result limits, but it is sufficient for correct invocation.

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 100%, so the schema already documents both parameters. The description adds an example goal for `query` ('make my dog look royal'), but does not elaborate on the `hub` filter or explain matching semantics beyond what the schema already provides.

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 names a specific verb+resource ('Browse or search Kavel's AI photo & video generators') and provides concrete examples. It does not, however, distinguish this tool from its siblings like list_kavel_models or build_kavel_prompt.

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?

It implies usage by suggesting how to use the `query` parameter, but offers no explicit guidance on when to choose this tool over alternatives such as open_in_kavel or build_kavel_prompt. No exclusions or prerequisites are stated.

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