tf_apply

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

No annotations provided, so the description must convey behavioral traits. 'Apply Terraform changes' does not disclose that this tool typically modifies infrastructure, may require confirmation, or can be destructive. No mention of side effects like state file updates or resource creation/deletion.

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 overly minimal (three words) and lacks any structure. While short, it is not concise because it omits critical information. Front-loading is not applicable as there is no content to front-load.

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 has 5 parameters with low schema coverage, no output schema, and no annotations, the description is severely incomplete. It fails to explain how to use complex parameters like 'var' (object) or 'target', and does not mention return values or error conditions.

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 description coverage is only 20% (only plan_file has a description). The description adds no meaning beyond the parameter names. For instance, 'dir', 'auto_approve', 'target', and 'var' remain completely undocumented, leaving the agent without guidance on their purpose or format.

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 states 'Apply Terraform changes' which identifies the verb and resource, but it's too vague given the many sibling tools like tf_plan, tf_destroy, etc. It does not specify what 'Apply' entails (e.g., executing a plan, creating resources) nor how it differs from generating a plan.

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_plan (to preview changes) or tf_destroy (to tear down). Does not mention prerequisites such as having a generated plan or initialized working directory.

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