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

With no annotations, the description carries the full burden and does disclose meaningful traits: the exact endpoint hit, that an API key is required, and that a 'split mode' narrows the response to the display name. It omits rate limits, failure behavior, and how 'split mode' is selected — notably that mode does not appear anywhere in the input schema, so an agent cannot actually request it.

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 tight sentences with no filler, and the endpoint plus the 'not this / use decide' routing are front-loaded after a brief framing question. The rhetorical opening costs a little density but sets context cheaply.

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 one-parameter lookup with no annotations and no output schema, the description covers the essentials: where the data comes from, that auth is needed, and roughly what comes back. The unexplained 'split mode' is the one dangling thread an agent cannot act on.

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 single parameter is documented in the schema ('Catalogue id, e.g. openai/gpt-5-6'), so the description adds little beyond restating it inside the URL template. Baseline 3 is appropriate when the schema already does the work.

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 opening question is a soft framing, but the following sentence makes the operation concrete: it reads a single model's card from https://modelspec.dev/api/models/<model_id>.json. It also distinguishes itself from one sibling ('Not current evidence or a ranking; use decide'), though it does not differentiate against rank, compare_models, or hardware_fit.

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?

It gives an explicit when-not ('Not current evidence or a ranking') and names the alternative to use instead ('use decide'), which is a real routing instruction. It stops short of stating the positive case ('use this when you want the static card for one model'), leaving the trigger condition implicit.

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