kie_catalog_show

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

With no annotations provided, the description carries the transparency burden. It discloses the content of the model card (input schema, limits, price) which is useful, but it does not state whether the operation is read-only, how it handles invalid model IDs, or any error behavior. Since it's a simple info tool, this is adequate but not rich.

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?

Two sentences, front-loaded with the core purpose, and no extraneous detail. The 'Call this BEFORE kie_generate' instruction is placed efficiently at the end. Highly concise and well-structured.

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 one-parameter tool with no output schema, the description is largely complete. It conveys what the tool returns (full model card with specific fields) and when to call it. Minor gaps like error handling or how to obtain model IDs are not critical for this low-complexity tool.

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% because the only parameter 'model' has a description 'model id'. The tool description does not add extra meaning beyond the schema, such as where to find valid model IDs or examples. Baseline of 3 applies since schema covers it.

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 shows a full model card including input schema, limits, and price. It distinguishes from sibling tools like kie_catalog_list by emphasizing the 'full model card' aspect, and explicitly mentions a key usage tie to kie_generate.

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?

Provides explicit guidance to call this tool BEFORE kie_generate, giving a clear when-to-use. However, it does not mention when not to use it or contrast with alternatives like kie_catalog_list, so it falls short of a 5.

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