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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a useful checklist of what the scan looks for, but says nothing about scan scope limits, runtime, permissions required, or whether findings are truncated — behavioral context beyond the annotation set is thin.

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?

A single front-loaded sentence: the core action comes first and the enumerated condition list follows. It is dense but every item names a distinct detectable failure mode, so nothing is padding; it only loses a point for being one long unbroken clause list.

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 an output schema present, rich annotations, and 100%-documented parameters, the description only needs to convey scope and coverage — which it does via the condition list. The remaining gap is routing guidance relative to sibling diagnostics, which is a real but limited omission for a low-complexity two-parameter read 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 description coverage is 100%: the parent parameter's resource-name format and the namespace parameter's optional scoping behavior are fully spelled out in the schema. The description merely reflects that same cluster/namespace duality in prose, adding no syntax, defaults, or edge-case meaning beyond the 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?

States a specific verb and resource ('Scans a cluster or namespace') and enumerates the concrete conditions it detects (CrashLoopBackOff, OOMKilled, node pressure, stalled rollouts, quota exhaustion, PDB blocks, webhook risks, APF issues). This clearly distinguishes it as a broad diagnostic sweep, though it never names the adjacent tools (get_k8s_cluster_health, diagnose_k8s_workload) it should be chosen over.

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?

Usage is only implied: an agent can infer this is a general issue-scan rather than a single-resource fetch. There is no explicit when-to-use/when-not guidance, no mention of when to prefer get_k8s_cluster_health or diagnose_k8s_workload, and no statement about cost or latency of a full-cluster scan.

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