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

Annotations already declare readOnlyHint=false, destructiveHint=false, so the safety profile is known. The description adds value beyond them: the precise state change made, and the failure contract that an unknown node is refused without changing anything.

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?

Three tightly packed sentences, front-loaded with the operation and its reversal-tool relationship, followed by usage conditions and input constraints. No filler sentences.

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 mutation tool with annotations covering safety and a fully described schema, the description supplies the remaining pieces an agent needs: usage triggers, name-resolution dependency, and error behavior. No output schema omission is a gap here.

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 node_name, cluster_id and dry_run are already documented in the schema. The description largely restates the node_name exactness/listing guidance already present in the schema field description, so 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 (uncordon) and resource (one Kubernetes node) and names the exact API mutation performed (spec.unschedulable=false). It explicitly differentiates itself from its sibling cordon_node by declaring itself the reversal of it.

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 explicit when-to-use conditions (a cordoned node returning to service, an abandoned consolidation, finished maintenance) and names the directional alternative cordon_node. It also tells the agent to call get_nodes to resolve the name, leaving no inference needed.

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