Get RouterBase model details

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

The description only says 'Fetch metadata' with no behavioral details such as whether it is read-only, any required permissions, rate limits, or side effects. With no annotations provided, the description carries the full burden and fails to disclose basic traits.

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 sentence with no wasted words. It is front-loaded and gets straight to the point.

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 has 2 parameters, no output schema, and no annotations, the description is insufficient. It does not explain what metadata is returned, any usage constraints, or the relationship to other tools. For a simple fetch it is barely adequate.

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%, so the baseline is 3. The description adds no extra meaning beyond what the schema already provides; it simply restates the purpose without detailing parameter formats or constraints.

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 action ('Fetch metadata') and the resource ('a specific RouterBase model id'). This is a specific verb+resource pair that distinguishes it from sibling tools like routerbase_chat_completion (different verb) and routerbase_list_models (different resource).

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 guidance is provided on when to use this tool versus the siblings. For example, it does not explain when to fetch details for a single model versus listing all models with routerbase_list_models. No preconditions or alternatives are mentioned.

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