serving_endpoints_list

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

Annotations already declare readOnlyHint=true, indicating safe read-only behavior. The description adds only the REST endpoint, which is minor. No additional behavioral traits (e.g., rate limits, pagination behavior) are disclosed, but there is no contradiction.

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 description is a single sentence that conveys the core purpose and REST endpoint without any fluff. It is front-loaded and efficient.

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 list operation with an output schema and read-only annotation, the description is adequate but lacks details on pagination behavior and typical return fields. It serves a minimum viable purpose but could be more informative.

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?

With 0% schema description coverage, the description must explain the parameters (page_size, page_token) but does not. The names and schema constraints provide some info, but the agent lacks guidance on their purpose (e.g., page_token for pagination).

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 clearly states 'List model serving endpoints' which is a specific verb+resource combination. It distinguishes this tool from sibling tools like serving_endpoints_get (get one) or serving_endpoints_create, and from vs_endpoints_list (vector search).

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?

The description implies usage through its name and action, but provides no explicit guidance on when to use this tool versus alternatives, nor does it explain pagination or context like 'use when you need all endpoints'. The REST endpoint is provided but that is standard.

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