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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral facts: the call is free, requires no API key, and the models themselves are not invoked through this server. It does not describe the response shape or price units (per token vs per image), which matters since there is no output schema.

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 short sentences, front-loaded with what the tool returns before the caveat about how to actually call the models. No filler and nothing repeated from the annotations or schema.

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-optional-parameter read-only lister with rich annotations and no output schema, the description supplies everything an agent needs: what is returned, that it costs nothing and needs no key, and the crucial fact that the returned models are called elsewhere.

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 `kind` parameter already carries its enum and default ('Defaults to chat.'). The parenthetical '(chat, images or audio)' restates the enum rather than adding semantics, so the baseline 3 is appropriate.

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 names a concrete resource (the AI models available through SingIt, split into chat/images/audio) and what comes back with it (prices). The line about the OpenAI-compatible API endpoints and 'not through these MCP tools' cleanly separates it from every sibling, which are all price/weather/crypto/profile lookups.

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 clear context for use: this is the discovery step for model choice, and actual model invocation happens over HTTP at the stated endpoints rather than via MCP. That is a strong implicit when/when-not. It stops short of an explicit routing sentence (e.g. 'call this before choosing a model'), and no sibling is named as an alternative.

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