compare_providers

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

Discloses all return values (cost per 1M tokens, savings ratio, source links) and implies read-only behavior, but could mention whether it fetches live data (assumed) or any authentication requirements. No annotations exist, so description carries burden.

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 concise, front-loaded sentences: purpose, outputs, and next step. No wasted words.

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 existence of an output schema (unknown details but present), the description adequately explains the tool's function and usage context for a simple comparison with one parameter.

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% with a clear enum description; the tool description adds no additional meaning beyond the schema's listing of provider options.

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?

Description clearly states it compares Gonka Network pricing against a competitor, names the specific outputs (cost per 1M tokens, savings ratio, source links), and distinguishes from sibling tools like calculate_savings and get_pricing.

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 clear usage context by suggesting to call calculate_savings afterwards, but does not explicitly state when not to use or compare against sibling tools like get_pricing.

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