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

Annotations already declare readOnlyHint=true, so safety is covered, and the description adds useful context beyond them: the underlying REST endpoint (GET /models/{model_name}) and the fact that the return is a catalog entry containing pricing, context length, and capabilities. That effectively compensates for the absent output schema, though error behavior and version-resolution semantics are not discussed.

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 compact sentences with zero filler; the purpose and returned fields are front-loaded, and the REST endpoint is a useful secondary detail rather than padding.

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 simple two-parameter read tool with no output schema, the description covers what is fetched (pricing, context length, capabilities) and how, which is enough for correct invocation. Only minor gaps remain, such as behavior when the model or version does not exist.

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%, so both parameters (model_name with slash handling, version defaulting to latest) are fully documented in the schema itself. The description adds no parameter-level detail beyond implying a single model lookup, which is the expected baseline when the schema does the heavy lifting.

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 gives a specific verb and resource ('Get one model's catalog entry') and enumerates the content returned (pricing, context length, capabilities), so the agent knows exactly what it fetches. The contrast with the sibling deepinfra_list_models is implied by 'one model' but never named, so it falls short of explicit sibling differentiation.

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 only implied: the singular 'one model' plus the required model_name parameter signal that this is the lookup path when a specific model is already known, versus list_models. There is no explicit statement of when to prefer this over alternatives and no exclusions or prerequisites mentioned.

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