list_cluster_pools

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

States read-only nature, which is key behavioral information. No annotations provided, so description carries full burden. Lacks details on pagination or limits but adequate for a simple list tool.

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?

Three sentences with no waste. Front-loaded with main action and returns. Efficient and easy to parse.

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?

Given simplicity (1 param, no output schema), description fully covers purpose, input origin, and usage context. No missing information relevant for calling the tool.

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 coverage is 100% with a clear description of service_id. Description adds mention of its origin (list_services) but repeats schema info. No additional semantic value beyond schema.

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?

Description clearly states it lists worker node pools of a managed Kubernetes cluster, specifies returned fields, and distinguishes from sibling write tools by explicitly stating that write operations are not exposed.

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?

Provides explicit use cases: inspect compute before scale change or find pool by name. Also clearly states it is read-only and that write operations are separate tools, guiding appropriate usage.

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