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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavior beyond that: lookups are strict and unknown models raise errors rather than returning fuzzy or hallucinated specifications, which tells the agent to avoid guessing identifiers.

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?

Two short sentences, zero filler, with the core action front-loaded and the strictness caveat immediately after. Nothing repeats the name or title.

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 read tool with annotations covering safety and an output schema covering returns, the description supplies the essential lookup contract. The only missing piece is a concrete identifier example or a pointer to list_accelerators for discovery.

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 0% for the single `model` field, so the description carries the burden — and it does meaningfully: the value may be either a full model name or a canonical slug, and it must be exact. It stops short of giving an example slug format, which would have fully closed the gap.

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?

States a specific verb and resource: fetch exactly one accelerator record, keyed by model name or canonical slug. The word "one" implicitly contrasts with the listing siblings, but no sibling is named, so the differentiation is only implied.

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?

Usage is implied: call this when you already have an exact identifier, since listing/discovery is elsewhere. There is no explicit "use list_accelerators to find a model" routing and no stated exclusions, so the agent must infer the alternative.

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