iac_terraform_state

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

The [SAFE] tag indicates a read-only operation, but without annotations, the description should disclose more prerequisites or side effects. It partially satisfies transparency.

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?

Single sentence with no fluff, front-loaded with safety hint. Minor omission of parameter explanation prevents a higher score.

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?

Lacks details on return value, parameter usage, and prerequisites. Despite low complexity, the description fails to fully equip the agent for correct invocation.

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?

The sole parameter 'workDir' is undocumented in both schema and description. With 0% schema description coverage, the description does not compensate by explaining its 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?

The description clearly states the tool shows Terraform state in JSON format, with a specific verb and resource. It is distinct from siblings like iac_terraform_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 versus alternatives. The [SAFE] prefix hints at safe usage but doesn't provide explicit context.

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