List available models

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

Without annotations, the description provides some behavioral context: it is a 'live' catalog and includes per-token pricing specifics. However, it does not mention whether the operation is read-only, pagination behavior, or any authentication requirements, leaving gaps for a tool with no annotations.

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 two sentences, with the key purpose (live catalog of all models) front-loaded and no redundant wording. Every detail (type, context window, pricing, filter tip) earns its place.

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 list tool, the description covers the return contents (type, context window, pricing) and filter behavior. It lacks details about ordering, pagination, or response format, but the absence of an output schema and the tool's simplicity make this acceptable.

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 schema already documents the 'type' parameter at 100% coverage. The description adds value by explaining the rationale for filtering ('keep the list short') and implying that omitting the filter returns all models, which goes beyond the schema's simple 'Filter by model type'.

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 catalogs all ApexApi models, listing type, context window, and USD pricing. This is a specific verb (catalog/list) with a clear resource (all models), distinguishing it from siblings like chat or get_balance.

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 implies when to use it (to view available models and pricing) and provides a usage tip ('Filter by type to keep the list short'). It does not explicitly name alternatives or exclusions, but no sibling tool offers a similar listing function, so the context is clear.

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