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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description 'Gets' is consistent with a safe read operation. The description adds minimal behavioral context beyond the scope ('specific node pool' vs list), but it doesn't disclose return format or error behavior. Since annotations cover the safety profile, this is acceptable but not rich.

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 with no filler words. It communicates the essential action and resource in under 20 words, perfectly sized for a simple getter tool.

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 the single parameter fully documented in the schema, strong annotations, and presence of an output schema, the description is mostly complete. However, it lacks any usage guidance relative to sibling list/get tools, which would make it more helpful. For a simple getter, this is a minor gap, so a score of 4 is appropriate.

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 schema provides 100% coverage for the sole parameter 'name,' including the exact resource format. The description adds no additional parameter semantics, so it relies entirely on the schema. This matches the baseline for high schema coverage.

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 the specific verb 'Gets' and identifies the resource as 'details of a specific node pool within a GKE cluster.' This clearly distinguishes it from list_node_pools and get_cluster, making the purpose unambiguous.

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 when you need details for one specific node pool, but it does not explicitly state when to use this tool over siblings like list_node_pools or get_cluster. There is no explicit when-not or alternative naming, so guidance is only implied.

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