orcarouter_model_card

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

No annotations are present, so the description bears full burden. It indicates a read-like operation (get info) but does not explicitly state it is non-destructive, mention authorization needs, rate limits, or potential error conditions. The behavior beyond the surface purpose is mostly opaque.

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?

A single, front-loaded sentence efficiently conveys the tool's purpose and key output fields. No wasted words; every element contributes.

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 (1 parameter, no output schema, no nested objects), the description covers the main output attributes. However, without an output schema, listing the exact fields would improve completeness. Still, it is mostly sufficient for a straightforward query tool.

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%, and the schema already provides a thorough description of the 'model' parameter including format and source. The tool description adds no further meaning to the parameter itself, so baseline 3 applies.

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 verb 'Get detailed information' and the resource 'a single model', listing specific attributes (pricing, context window, endpoints, latency). This distinguishes it from sibling tools like orcarouter_models_list (which lists models) and orcarouter_chat (which uses 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?

The description implies use when detailed info for one model is needed, but does not explicitly contrast with siblings or state when not to use it. No exclusions or alternatives are provided; guidance is only implied.

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