terraform

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Execute Terraform commands' implies this is an execution tool, it doesn't disclose critical behavioral traits: whether commands are destructive (like 'destroy'), what permissions are needed, whether it modifies infrastructure, what happens on failure, or any rate limits. The mention of 'destroy' in the examples hints at destructive potential but doesn't explicitly warn about it.

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 extremely concise - a single sentence with parenthetical examples. It's front-loaded with the core purpose and wastes no words. Every element earns its place, though it could benefit from additional context given the tool's complexity.

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?

For a complex infrastructure tool with 12 parameters, no annotations, no output schema, and 0% schema description coverage, the description is severely incomplete. It doesn't explain what Terraform is, what the commands do, what the expected outputs are, or any behavioral characteristics. The agent would struggle to use this tool correctly without significant external knowledge.

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?

With 12 parameters and 0% schema description coverage, the description provides no parameter semantics whatsoever. It doesn't explain what 'action' does, what 'workingDir' means, how 'varFiles' or 'vars' are used, what 'autoApprove' controls, or the purpose of any other parameters. The description fails to compensate for the complete lack of schema documentation.

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 clearly states the tool's purpose: 'Execute Terraform commands' with specific examples (init, plan, apply, destroy, validate, output, etc.). It uses a specific verb ('Execute') and identifies the resource ('Terraform commands'), but doesn't explicitly differentiate from sibling tools like AWS CloudFormation or other infrastructure 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?

The description provides no guidance on when to use this tool versus alternatives. With many sibling tools available (AWS CloudFormation, various AWS services tools, Ansible tools), there's no indication of when Terraform is preferred over other infrastructure-as-code or cloud management tools. No context about use cases or prerequisites is provided.

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