Read cluster desired and observed state

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 by structured data. The description adds no behavioral context beyond that—nothing about size of the payload, consistency of desired vs observed state, or whether the call fails for nonexistent clusters.

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?

It is a single front-loaded sentence with no filler. The problem is under-specification rather than verbosity—the one sentence simply repeats the title instead of front-loading any decision-relevant detail.

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 tool with an undocumented required cluster identifier, an optional namespace, no output schema, and many overlapping cluster readers, the description is far too thin. An agent cannot determine what the return value covers or how it differs from cluster_status_get, cluster_diagnose, or cluster_members_list.

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% for the top-level parameters: the required 'cluster' parameter has only a pattern and length bounds, with no indication of what identifier format or source is expected. The 'namespace' reference is documented inside $defs, but the description adds no meaning for either parameter and does not explain the optional namespace scoping.

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 prerequisite, and no mention of any alternative. With 90+ siblings including an obvious overlap like cluster_status_get, the agent is left to guess which read tool to call, and the description does nothing to resolve that ambiguity.

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