get_openrouter_best_value

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

No annotations provided, so description carries full burden. It only states the tool returns best value models, but does not disclose authentication needs, rate limits, caching behavior (though use_cache parameter hints), or selection methodology (how 'best value' is computed).

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?

Single sentence conveying purpose and differentiation. Front-loaded and efficient with 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?

While the tool is simple and parameters are clear, the description lacks explanation of how 'best value' is defined (e.g., which metric for performance vs cost). No output schema means agents need more context on return structure, but siblings have similar brevity.

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 both parameters described. The description adds no extra meaning beyond the schema; it does not explain how the limit affects results or further details on the use_cache parameter.

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 it returns 'best value LLM models on OpenRouter' and defines 'best value' as 'best performance vs cost ratio'. It distinguishes from sibling tools like get_openrouter_models (all models) and get_openrouter_popular (popular models).

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?

No explicit guidance on when to use this tool versus alternatives like get_openrouter_models or get_openrouter_popular. The description only implies it for cost-performance optimization, but lacks when-not-to-use or alternative mentions.

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