cordon_node

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

Lacks additional context beyond the name. No annotations exist, so description should disclose behavior: it only prevents new scheduling, doesn't evict pods. Missing safety notes, auth requirements, or reversibility. Minimal value added.

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?

Single sentence conveys core purpose with no wasted words. Front-loaded and easy to parse.

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?

Despite tool simplicity and full schema coverage, description omits important context: that cordoning alone does not drain pods, and that uncordon_node reverses it. For a tool interacting with node lifecycle, this is a notable gap.

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 coverage is 100% and sufficiently describes each parameter (dryRun, cluster, nodeName). Description adds no extra meaning beyond schema, so baseline 3 is appropriate.

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?

Clear verb+resource combination: 'Marks a node as unschedulable.' Unambiguously states the action and target. Distinguishes from siblings like uncordon_node (reverse) and drain_node (cordon+evict).

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?

No guidance on when to use vs alternatives (uncordon, drain, taint). Does not mention prerequisites, typical use cases (e.g., node maintenance), or when to avoid.

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