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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true. The description adds beyond that: 'live pricing' implies real-time data (not static), and 'Models work as drop-in replacements for OpenAI and Anthropic — same SDK, same API calls' is a key behavioral trait for API invocation. It also discloses the return format (model IDs usable directly in openai.chat.completions.create, status, USD per 1M tokens), which enriches the agent's expectation of the tool's output.

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 four sentences, front-loaded with purpose, then usage, then return format, then next-step guidance. Every sentence earns its place: no redundancy, no filler, and the structure logically progresses from what → when → output → follow-up. It is concise yet information-dense.

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 the tool's simplicity (zero params, output schema present, strong annotations), the description is complete. It covers purpose, usage context, behavioral compatibility, output fields, and a suggested subsequent action. The presence of an output schema means detailed return documentation isn't necessary, but the description still provides a useful summary. No gaps remain for an agent to select and invoke this tool correctly.

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, so the schema fully covers all parameters (vacuously). The description adds no parameter-specific information because none is needed. The baseline for zero-parameter tools is 4, and the description appropriately focuses on usage and output rather than inventing parameter detail.

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 opens with a specific verb and resource: 'List all AI models available on Gonka Network with live pricing.' It clearly states the deliverable (model IDs, status, USD per 1M tokens) and differentiates from siblings by emphasizing live pricing and drop-in OpenAI/Anthropic compatibility. The use case ('when user asks which model to use or wants alternatives to GPT-4o / Claude') further distinguishes it from tools like calculate_savings or compare_providers.

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 explicitly states when to use the tool: 'Use this when user asks which model to use or wants alternatives to GPT-4o / Claude.' It also provides a workflow directive ('After this: call calculate_savings() to see annual savings with these models'), which is actionable guidance. While it doesn't list 'when not to use' scenarios, the positive guidance and chaining to a sibling make the usage intent unambiguous.

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