k8s_drain_node

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

Discloses key behaviors: evicts all pods, cordons automatically, and effects of force/ignore_daemonsets. However, it omits details on timeout, delete_local_data, side effects like unschedulable state, and failure handling.

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 well-structured sentences with no redundant content. First sentence provides primary purpose, subsequent ones add parameter-specific guidance.

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 6 parameters, no output schema, and no annotations, the description covers only two parameters in depth. Missing explanation of timeout, delete_local_data, return values, and error scenarios.

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?

Adds meaning for 'force' and 'ignore_daemonsets' beyond the schema. Yet with 0% schema description coverage, the description does not cover 'timeout', 'delete_local_data', 'context', or 'node_name', leaving gaps.

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?

Description clearly states the action (drain), resource (node), and purpose (maintenance). It also mentions automatic cordoning, distinguishing it from sibling cordon tools.

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?

Provides context on automatic cordoning and hints for using 'ignore_daemonsets' and 'force' parameters. However, it does not explicitly state when to use this tool versus alternatives like cordon or delete node.

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