tf_init

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

With no annotations, the description carries full burden but only says 'Initialize', which is vague. It fails to disclose that initialization may download providers, modify state backend config, or require specific permissions. No destructive or idempotent behavior is mentioned.

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 sentence with no fluff. However, it could benefit from additional details without becoming verbose. Still, it is appropriately sized for a tool name that is self-explanatory to some extent.

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 complexity of Terraform init (e.g., backend config, provider locks), the description is incomplete. No output schema exists, yet the tool likely returns output (e.g., success message, errors). The description provides no coverage of these aspects.

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?

Schema description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond the schema parameter descriptions ('Working directory', 'Upgrade providers'). It does not explain when to set 'upgrade' to true or implications.

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 'Initialize Terraform working directory' clearly states the specific verb and resource. It distinguishes tf_init from sibling tools (e.g., tf_plan, tf_apply) which perform different actions.

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. There is no mention of prerequisites, typical workflow position (e.g., first step), or when not to use it.

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