tf_taint

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

With no annotations, the description carries full burden. It does not disclose that this is a Terraform taint command affecting state, that it requires an existing resource, or that changes take effect on next apply. Insufficient behavioral detail.

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?

Extremely short (4 words) but not well-structured. While concise, it lacks a full sentence and may be too terse to be helpful. The phrase 'for recreation' could be rephrased for clarity.

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 complexity of Terraform commands and 25 sibling tools, the description is woefully incomplete. No mention of directory parameter, state implications, or relationship to tf_plan/tf_apply.

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% (no param descriptions). The tool description does not mention parameters at all, adding zero value beyond the schema. For 2 parameters, this is inadequate.

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?

The description 'Mark resource for recreation' clearly states the verb (mark), resource (resource), and purpose (for recreation). It distinguishes from siblings like tf_untaint (unmark) and tf_destroy (destroy). However, 'recreation' may be ambiguous without Terraform context.

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 this tool vs alternatives like tf_untaint, tf_apply, or tf_destroy. Lacks context for appropriate usage and prerequisites.

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