tf_plan

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

With no annotations and a bare description, the tool's behavioral traits (e.g., read-only nature, prerequisites, side effects) are entirely undisclosed. The description does not beyond what is obvious from the name.

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?

The description is a single sentence, but it is under-specified rather than concise. It lacks critical context that would make it useful.

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 complexity (4 params, no output schema, many siblings) and lack of annotations, the description is grossly insufficient. It omits essential details like Terraform command, plan output, and prerequisites.

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 75% with three parameters documented. The description adds no extra meaning to parameters; baseline 3 is appropriate as the description does not detract but also adds nothing.

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 'Create execution plan' is essentially a tautology of the tool name 'tf_plan'. It fails to specify the Terraform context or distinguish what an execution plan is.

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 is provided on when to use this tool versus its siblings like tf_apply or tf_destroy. The description gives no context for selection.

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