Get AIOrouter Model Info

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

Annotations declare readOnlyHint=true, and the description describes a read-only operation with no contradiction. The description adds value beyond the annotation by specifying the exact fields returned (provider, context window, etc.), giving the agent expected output shape even without an output schema.

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 a single, front-loaded sentence: 'Get detailed info for a single AIOrouter model' immediately states the action, followed by a compact list of data fields. No wasted words; every element contributes to understanding the tool.

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 single-parameter read-only tool, the description is complete. It covers the purpose, the scope (single model), and the return content (list of fields), compensating for the lack of an output schema. There are no hidden prerequisites or side effects to disclose.

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 input schema fully describes the only parameter 'model' with an example ('deepseek-v4-pro'). The description doesn't add extra syntax or format details, so the schema carries the semantic load. Baseline 3 applies for high schema coverage.

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 a specific action ('Get detailed info') on a specific resource ('a single AIOrouter model') and enumerates the content (provider, context window, max output, capabilities, pricing, supported parameters). This distinguishes it from sibling tools like aiorouter_list_models (bulk list) and aiorouter_compare_models (comparison).

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 the right use case: when you need detailed info about one specific model. However, it does not explicitly mention alternatives or when not to use it (e.g., for a bulk list use aiorouter_list_models, for pricing-only use aiorouter_get_pricing). Clear context but no exclusions.

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