iac_scan_terraform

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'scan' but does not explicitly state whether the tool is read-only, whether it modifies files, whether an API key is needed for certain features, or what the output looks like. For a security scanning tool, these are significant behavioral details that are missing.

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, front-loaded sentence with no extraneous words. It efficiently captures the action, target, and scope of checks, making it easy for an agent to parse quickly.

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?

With no output schema and no annotations, the description needs to explain the tool's return value or side effects, but it does not. An agent is left without information about what the scan produces (findings, report, exit code), whether the scan is non-destructive, or if the api_key is required for Pro/Enterprise scans. This is a substantial gap for a security tool.

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 schema provides descriptions for both parameters (directory and api_key), achieving 100% coverage. The description adds no additional parameter-level meaning beyond what the schema already documents. This matches the baseline of 3 for high schema coverage.

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 states a specific verb ('Scan'), a resource ('Terraform files'), and the purpose ('security misconfigurations and best practice violations'). It clearly differentiates from sibling tools like iac_scan_docker and iac_scan_k8s by naming Terraform explicitly.

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 implies usage for scanning Terraform configurations, but it does not provide explicit guidance on when to use this tool versus alternatives like iac_scan_docker or iac_scan_k8s. There are no exclusions or conditions stated, leaving the agent to infer the appropriate context from the tool name and description.

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