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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered. The description adds useful context that third-party scores carry their source and date and that the site's own testing status is reported, but says nothing about error behavior for a bad slug or about data freshness beyond the score dates.

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 opened by the scope ("One model:") followed by a compact field list; every clause adds information. The list format is slightly dense but no sentence is wasted.

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?

With no output schema, the description usefully characterizes what a caller gets back — parameters, license, context length, weight options with size and memory, scored benchmarks with provenance, and links. That covers the main gaps; only failure modes and staleness handling are omitted.

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 description coverage is 100% and the single slug parameter already documents its origin (find_models) and max length. The description adds no further meaning about the slug that the schema does not already provide, so the baseline 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?

"One model" plus an enumeration of returned fields makes it clear this is a single-record detail lookup, which implicitly contrasts with the list-oriented find_models sibling. It lacks an explicit verb, but the resource and scope are unambiguous.

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 never says when to use this versus find_models or compare_models; the only routing signal ("slug from find_models") lives in the schema, not the description. An agent gets no explicit guidance about prerequisites or alternatives.

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