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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds valuable behavioral context, specifically that the location parameter accepts a region, zone, or '-' for all locations, and that listing is scoped to a given project and location. No contradictions with annotations.

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, front-loaded sentence that directly states the core functionality and the most important usage nuance (location wildcard). There is no redundant or extraneous information, making it highly concise 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?

The tool is simple (one parameter, read-only) and the output schema exists, so return-value details are covered externally. The description conveys the essential purpose and the key location behavior. A small gap is the lack of any mention of pagination or whether only active operations are returned, but these may be addressed by the output schema, and the simplicity of the tool keeps it mostly complete.

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% for the 'parent' parameter, with detailed format ('projects/*/locations/*') and explanation of '-' wildcard already provided in the schema. The tool description paraphrases the location flexibility but adds little new semantic value beyond what the schema already documents, so the baseline score of 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 uses a specific verb ('Lists') and identifies the exact resource ('GKE operations') and scope ('in a given project and location'). It clearly distinguishes from sibling tools like get_operation (single operation) and cancel_operation (mutation) by focusing on the listing behavior.

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 clarifies the scope (project and location) and notes the wildcard '-' for all locations, which implies when it might be used (e.g., to list across all zones/regions). However, it does not explicitly mention when to use this tool versus alternatives like get_operation, leaving the usage context somewhat implied rather than spelled out.

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