tf_list_files

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

With no annotations provided, the description must disclose behavioral traits. It fails to specify whether the listing is recursive, what file types are included (only .tf?), or if directories are listed. The agent cannot infer the operation's safety or side effects.

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 (one phrase), which is efficient for a simple tool. However, it could add a few more details without becoming verbose, such as the file listing behavior (e.g., non-recursive, .tf files only).

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 absence of an output schema, the description should indicate the output format (list of filenames? full paths?). It also fails to differentiate from 24 sibling tools, many of which also operate on Terraform files. The description is incomplete for effective tool selection.

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 single parameter 'dir' has 0% schema description coverage and no explanation in the description. The description only mentions 'directory' in the purpose but does not clarify if it is required, what format it expects, or the default value. This is insufficient for a tool with one undocumented parameter.

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 verb ('List') and resource ('Terraform files') with a location ('in directory'). It is specific enough for a basic understanding, but could be improved by specifying file extensions (e.g., .tf) to distinguish from other file types.

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 its siblings (e.g., tf_read_file for reading content, tf_show_plan for plans). There is no mention of prerequisites like being in a Terraform directory or that it is a read-only operation.

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