timps_cloud_cost_auditor

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 does not state whether the tool is read-only, what side effects might occur (e.g., AWS CLI calls), what permissions are needed, or what the output format is. The description implies an audit but doesn't clarify if it mutates anything or only reports.

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, relatively concise sentence covering both main actions. It's front-loaded with the purpose. However, the sentence is dense and jumps between two concepts (Terraform scanning and AWS CLI checking) without clear structural separation.

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 annotations, no output schema, and a single optional parameter, the description must carry significant context. It mentions what it scans but omits what the results look like, how to interpret findings, whether it writes any files, and what environments it supports. This is incomplete for a tool that combines IaC scanning with live CLI checks.

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 input schema has one parameter (repo_path, optional) with 0% description coverage. The description never mentions repo_path or what it represents (e.g., GitHub repo path, local filesystem path). Since the schema provides no defaults or descriptions, the description should have explained this parameter, and it doesn't.

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 primary action: scanning Terraform configs for waste and checking AWS CLI for idle resources. This gives a specific verb (scan/check) and resources (Terraform configs, AWS CLI). However, it doesn't explicitly differentiate from similar sibling tools like timps_cost_optimizer or timps_finops_agent, which could overlap in purpose.

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 the tool is used to audit Terraform configs and AWS CLI resources, but it provides no explicit guidance on when to use this tool versus alternatives like timps_terraform_plan_reviewer or timps_cost_optimizer. No when-not-to-use or prerequisite conditions are stated.

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