Get a security-hardened starting template

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

With no annotations, the description carries the burden of behavioral disclosure. It states that templates are 'test-verified to contain no Critical or High findings' and that the tool returns Terraform plus notes on what still needs user input. This conveys safety, reliability, and limitations beyond the basic 'Get' action.

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?

Three sentences deliver purpose, usage guidance, and output expectation with no filler. The action and examples are front-loaded, and each sentence earns its place.

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?

The tool has a single parameter and an output schema, so the description does not need to detail return fields. It covers what the tool produces, why to use it, and what remains for the user to provide, which is sufficient for an agent to invoke it correctly.

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 schema provides no description for resource_type, so the description must compensate. It clarifies the expected value with five concrete examples across AWS, Azure, and GCP, giving an agent enough grounding to populate the only parameter correctly.

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 states a specific verb and resource: 'Get a security-hardened Terraform template for a resource type,' with concrete examples such as 'aws_s3_bucket' and 'azurem_storage_account.' This makes the tool's purpose unmistakable and clearly distinguishes it from sibling tools like scan_ferraform or explain_finding, which address different tasks.

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 explicitly advises 'Prefer this over writing the resource from memory' and gives the rationale that provider defaults are frequently insecure. This is clear usage context, though it does not enumerate exclusions or explicitly compare against sibling tools.

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