arvan_iac_tfsec

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

The description says 'Scan', which implies a read-only operation, yet annotations set readOnlyHint=false, creating a contradiction. No additional behavioral details are given, such as whether the tool writes or modifies anything.

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 only one sentence and very brief, but it omits critical information. It is concise but at the expense of completeness.

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 two optional parameters and no output schema, the description is severely lacking. It does not explain input format, return value, or usage context, making it unhelpful 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 description provides no information about the two parameters ('files' and 'directory'). With 0% schema description coverage, the description fails to explain what these parameters do or how to use them.

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 scans Terraform for security issues using tfsec, which is a specific verb and resource. It differentiates from sibling tools like arvan_iac_checkov or arvan_iac_tflint by naming the specific scanner.

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 alternatives, nor any prerequisites or exclusions. It does not mention that it is for static analysis of Terraform code only.

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