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

Annotations already mark it read-only, idempotent, non-destructive, and non-open-world. The description adds account/grant prerequisites, error codes, and return-field behavior, including served_model; that is useful behavioral context beyond annotations, though the served_model sentence is muddled.

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 core purpose is front-loaded, but the single sentence is long, heavily punctuated, and includes an unclear 'There, every other answer carries served_model' clause that weakens structure. It is information-dense but not concise.

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 parameters and no output schema, the description must carry return-value and prerequisite context; it enumerates returned fields and error cases. It is largely complete for a zero-parameter read-only listing tool, despite ambiguous response structure.

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?

There are zero parameters, so parameter semantics are not applicable; per baseline this scores 4. The description does not need to explain arguments.

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 identifies the resource as the models reachable by the account, including own and shared projects, and enumerates returned fields. It is clear what is being listed, though it never names or contrasts sibling tools such as open_model or check_model.

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 prerequisites: requires a moddl-account connection and whole-account grant, with named errors otherwise, and indicates a fallback to open-model scope. It does not explain when to choose list_models over check_model/open_model or when listing is unnecessary.

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