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

readOnlyHint=true already establishes the safe-read profile, and the description still adds real behavioral context: the payload carries total/returned/truncated/scope, and non-ready nodes sort first. That truncation and ordering behavior is not derivable from annotations or the schema and materially affects how an agent should interpret results.

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?

Purpose is front-loaded in the first sentence, followed by return-content detail and then alternative-tool routing. The external_ip explanation is a bit long for its value, but no sentence is redundant or filler.

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 no output schema, the description usefully compensates by enumerating the returned fields, the payload envelope (total/returned/truncated/scope), and the sort order. It leaves some gaps around result limits and pagination behavior, but is sufficient for correct invocation of a read-only two-parameter 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%, so both parameters (name, cluster_id) are already fully documented in the schema and the description adds no syntax, format, or filtering semantics for them. The field-level IP/hostname discussion describes return data, not inputs, so the baseline 3 applies.

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 ("Fetch node information from the cluster") and enumerates the returned facets: status, roles, capacity, allocatable resources, conditions, and network addresses. It partially separates itself from a sibling by routing SSH jump-host lookups to get_cluster_bastion, but never distinguishes itself from the similarly named list_cluster_nodes, so it falls short of full sibling differentiation.

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?

Gives an explicit when-to-use-another-tool condition: "For the SSH jump-host public IP of an Ankra-provisioned cloud cluster, use get_cluster_bastion," plus the condition under which external_ip is populated. However, it offers no guidance on when to prefer this over list_cluster_nodes or how node currently-returned scoping should drive the call.

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