arvan_iac_terraform_cost

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

The description implies a read-only operation (estimate cost), but annotations set readOnlyHint=false, creating an annotation contradiction. No behavioral details beyond the tool name, so the agent gets conflicting signals.

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, which is concise but lacks critical details. It's not overly verbose, but the brevity comes at the cost 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 two unannotated parameters and no output schema, the description fails to provide essential context like parameter roles, expected output, or prerequisites. The agent cannot properly invoke the 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?

Schema has 0% description coverage for both parameters (files, directory). The description does not explain their meaning or usage, leaving the agent without any guidance on how to provide input.

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 specific action: 'Estimate Terraform cost' using Infracost, distinguishing it from other Terraform-related tools like plan or apply. It's a concise verb-resource pair with a specific tool reference.

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 description lacks any context on prerequisites, suitable scenarios, or exclusions, leaving the agent to infer usage.

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