List Kenari Media Models

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

Annotations already indicate a safe read-only operation, and the description adds useful auth context by stating that the call is public and requires no key. It does not discuss pagination or empty-result behavior beyond the schema-level note about video, but with readOnlyHint=true and an output schema present, the behavioral disclosure is adequate.

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 short, front-loaded, and contains no filler. The second sentence earns its place by adding the auth requirement. It loses a point only because the first sentence largely restates the tool title rather than adding substantially new information.

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?

For a simple read-only listing tool with one optional parameter and an output schema, the description is complete enough. An agent knows what the tool does, that no auth is needed, and that modality filtering is available, while the schema and annotations cover the remaining details.

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?

The input schema fully documents the single optional parameter, including its enum values, filtering semantics, and the caveat that the video list may be empty. The tool description itself adds no parameter-level meaning, so the baseline score of 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 states a specific verb (List), a concrete resource (Kenari media-capable models), and narrows the scope to image/video. This clearly differentiates it from the sibling generation and editing tools, which perform actions rather than list catalog data.

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 gives clear context: this is a discovery/catalog tool for available media models, and the 'Public, no key needed' note signals that it can be called without setup. It does not explicitly state when-not-to-use it or name alternatives, but no sibling tool performs the same listing function, so the usage context is reasonably clear.

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