Search APIKO models

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-redundant context: the results are scoped to the calling API key, the call is free, and text models are not invocable through this server. It stops short of describing result ordering or pagination behavior.

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?

Three short sentences, zero filler, and the highest-value instruction ('use it before get_model') is front-loaded alongside the purpose. Every clause carries information the agent acts on.

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?

No output schema exists, and the description compensates by naming the returned fields (category, list prices, generation modes). Combined with annotations covering safety, an agent has enough to call this correctly; only minor operational details like result ordering or total-count behavior are absent.

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 description coverage is 100%: limit, query and category are all documented, including the category enum and defaults. The description only echoes the category values ('image / video / chat') and adds no syntax or format detail beyond the schema, so baseline 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?

States a specific verb and resource (list APIKO models usable by this API key) and enumerates the returned fields: category, list prices, generation modes. It is clearly distinguished from sibling get_model, which the description explicitly positions as the follow-up step.

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?

Gives explicit sequencing ('Use it before get_model; never guess model ids') and an explicit exclusion (text models are listed for reference only and must be called via the OpenAI-compatible API, not this server). That is exactly the when/when-not/alternative coverage an agent needs.

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