k8s_taint_node

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

No annotations provided, so description carries the burden. Discloses that NoExecute evicts pods, but does not mention idempotency, overwriting behavior, or if node must be scheduled/unscheduled. Missing side effects like potential pod rescheduling.

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?

Short and front-loaded, but omits critical parameter info. Could include parameter descriptions in the same number of sentences. Efficiency is poor because the space is not used to convey necessary semantics.

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 moderate complexity (5 parameters, no output schema, no annotations), the description only covers the 'effect' parameter and general purpose. Missing guidance on context requirements, required parameters, and expected behavior. Incomplete for safe and correct 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?

Schema coverage is 0%, yet description only explains the 'effect' parameter (listing valid values). Key, value, node_name, and context are entirely unexplained. The agent cannot infer appropriate values for 4 out of 5 parameters from the description.

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 'Add a taint to a node' and explains the concept of taints. Differentiates from sibling k8s_untaint_node implicitly by naming, but does not explicitly contrast.

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 general use (repel pods without tolerations) but lacks guidance on when to use specific effects, prerequisites (node must exist, context), or when not to use this tool versus alternatives like cordon/drain.

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