kie_catalog_list

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

With no annotations, the description effectively discloses key behavioral traits: prices are fetched live and never stored, schemas come from a 30-day cache, and the first call incurs a delay. This gives the agent useful expectations about data freshness and latency, going beyond the basic function.

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 brief and front-loaded with the core purpose, followed by two clarifying behavioral notes. It is efficient with no redundant wording, though the first phrase is a fragment rather than a complete sentence.

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 covers data freshness and latency, but given that no output schema exists and there are 11 sibling tools, it lacks explicit guidance on use cases and return contents. It is sufficient for a simple list tool but leaves the agent to infer when to use it.

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 already provides 100% coverage with descriptions for mode, type, and query. The tool description adds no additional parameter semantics, so the baseline of 3 is appropriate.

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 starts with 'Models with prices and limits,' which implies a listing operation but lacks an explicit verb like 'list' or 'retrieve.' The tool name kie_catalog_list clarifies the purpose, and the description distinguishes it by mentioning live prices and cached schemas, but it doesn't explicitly contrast with sibling tools like kie_catalog_show or kie_catalog_refresh.

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 does not state when to use this tool versus alternatives. It provides behavioral details about live fetching and caching but no guidance on when to choose kie_catalog_list over kie_catalog_show or kie_catalog_refresh. No exclusions or alternative tool mentions are present.

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