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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context above that bar — account-specific pricing, that the strongest models are locked until first purchase, and the meaning of the locked "key_limit" state — but it never describes the shape of the returned list or ordering.

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?

The opening clause is front-loaded and dense with useful information, but the trailing fragment about locked "key_limit" reads as a pasted field note with no structure or quotation and interrupts the flow. It is compact but not cleanly organized.

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 explaining return values, and it does so reasonably — model identity, free daily turns remaining, typical and maximum credits per message, locked state, and the key_limit flag. For a zero-parameter read-only listing that is close to sufficient; only ordering and record shape are left implicit.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly focuses its words on output meaning instead of inventing input semantics.

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 states the concrete resource and scope: the language models the Director can plan with, plus per-model cost for this account (free turns left from the daily budget, or credits per message typical/at-most). It is clear what the tool returns, though it never states an explicit verb like "lists" and never names list_models to distinguish itself from the sibling listing tool.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer that this is the Director-specific pricing listing and that list_models covers other cases; nothing in the text routes it.

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