kie_catalog_refresh

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 it ignores the cache and forces a re-read, and clarifies that prices are otherwise fetched live. However, it doesn't mention any potential side effects or return behavior, though for a non-destructive refresh this is likely acceptable.

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 sentences, front-loaded with the core action, then the rarity and usage condition. Every sentence adds unique value without 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 zero parameters and no output schema, the description is sufficiently complete: it explains what it does, when to use it, and why it's rarely needed. It doesn't clarify the return value, but that's likely low-stakes for a refresh action.

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 tool has zero parameters, with an empty schema, so there are no parameter details needed. The description provides context about what is refreshed, covering the only relevant semantics.

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 forces a full re-read of prices and model schemas, ignoring the 30-day schema cache. This uses a specific verb and resource, and distinguishes it from siblings like kie_catalog_list and kie_catalog_show.

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?

Explicitly says 'Rarely needed' and 'Use it when a model is missing or its parameters look wrong', providing clear conditions for use and when not to use it, contrasting with the default live-fetch behavior.

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