List Yorai models

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

The annotations already cover read-only semantics, so the bar is lower. The description adds useful context that it returns the starting price, which is not stated in the schema and is not obvious from the name alone.

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?

It uses two tight sentences with no filler, and the main capability is front-loaded before the filtering detail.

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?

The description is complete for a filtered-list tool: it names the resource, the returned price, and the filters. However, it does not mention pagination or whether results are limited, which leaves a gap for an agent that expects a long list.

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 description adds the allowed category values and supplies type examples that extend beyond the short property hints. Schema coverage is 75%, and the description usefully clarifies the two vaguely documented parameters (type and provider).

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 and resource: 'List models in the Yorai catalog with their starting price.' It is immediately distinguishable from siblings such as yorai_get_model (single model) and yorai_quote (pricing calculation).

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 tells the agent to filter by category (chat, image, video, audio), type, or provider slug, which gives clear usage context. It does not name an explicit alternative, but does state that filtering is the intended path over fetching individual models.

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