uncordon_node

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

Includes risk label '[WRITE][risk=medium]' and describes the dry_run behavior. Since no annotations are provided, the description carries the full burden, and it sufficiently discloses the write operation and preview feature.

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?

Front-loaded with purpose, then structured as a short docstring with parameter list. Every sentence is informative and concise, with no wasted words.

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?

Given the tool's simplicity and lack of output schema, the description covers key aspects: purpose, inverse, dry_run, and parameter details. It could mention failure scenarios or prerequisites, but it is largely complete for basic usage.

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?

The input schema has 0% description coverage, but the description explains each parameter: name (refers to node_list), dry_run (preview behavior), target (k8s config source). This adds meaningful context 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?

Clearly states the verb 'Mark', resource 'node', and effect 'schedulable'. Also mentions the inverse tool 'cordon_node', making the purpose unambiguous.

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?

Explicitly describes the dry_run option for previewing, and mentions the inverse operation. However, it does not provide explicit exclusions or when-not-to-use scenarios beyond the inverse.

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