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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond them: the sort order (newest first), the returned fields (context length, price per million tokens), and an auth/integration prerequisite. It does not cover pagination behavior for the limit, which keeps it from a 5.

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 no filler; the scope and shape of the result are front-loaded, and the prerequisite is stated last.

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 carries the burden of describing returns and does so (ordering and key fields). It leaves minor gaps — exact identifiers returned and paging behavior — but is sufficient for a simple zero-required-parameter read.

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 the two parameters (limit, search) are already documented in the schema; the baseline of 3 applies. The description adds no parameter-level detail such as what search matching covers or default paging behavior.

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 (list) and resource (AI models) plus scope (the workspace's OpenRouter key) and ordering (newest first). No sibling tool lists models — get_ai_settings/update_ai_settings are clearly different — so an agent can pick this out from the sibling set without opening a schema.

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?

'Needs the key connected' gives a useful precondition for when this will succeed, but there is no explicit when-to-use framing (e.g., before choosing a model for AI settings) or mention of alternatives. Usage is only implied by the resource name.

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