Read observed cluster status

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds no behavioral context of its own — nothing about whether "observed" status is live-queried or cached, how stale it may be, or what happens when a cluster is unreachable.

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?

Four words is short, but here brevity is under-specification rather than efficiency — the sentence is front-loaded only because there is nothing behind it. Every sentence earns its place only vacuously, since the sole sentence duplicates the title.

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 two-parameter read tool with no output schema and 0% parameter documentation, the description should carry the burden of explaining the parameters and the observed-vs-desired distinction. It does neither, leaving the definition incomplete relative to the sibling surface it must be distinguished from.

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 0% at the top level: the required "cluster" parameter has only a regex pattern and no stated meaning, and "namespace" is an optional filter whose role is never mentioned. The description supplies no clarification at all, so the agent cannot tell what "cluster" identifies or when to pass a namespace.

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?

Tautological: description restates name/title.

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?

There is no when-to-use guidance, no prerequisites, and no naming of alternatives, despite many closely related siblings (cluster_get, cluster_diagnose, cluster_metrics_get, cluster_placement_get, cluster_balancer_get) whose boundaries an agent must infer on its own.

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