localstack-deployer

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

The description adds valuable context beyond annotations: it specifies that the tool works with CDK, Terraform, and CloudFormation, and mentions 'deploys or destroys' which aligns with the destructiveHint=true annotation. While annotations cover safety (destructive, non-idempotent, non-readonly), the description clarifies the scope (AWS infrastructure on LocalStack) and methods (CDK/Terraform), providing useful behavioral context without contradiction.

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, efficient sentence that immediately communicates the core functionality. It's front-loaded with the essential action and context, with zero wasted words or redundant information. Every word earns its place in conveying the tool's purpose.

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 tool's complexity (6 parameters, destructive operations, multiple project types) and lack of output schema, the description provides basic context but could do more. It covers what the tool does but doesn't address potential side effects, error conditions, or what happens after deployment/destruction. The annotations help with safety context, but for a tool with destructiveHint=true, more behavioral guidance would be beneficial.

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?

With 100% schema description coverage, the input schema already documents all 6 parameters thoroughly. The description doesn't add any parameter-specific semantics beyond what's in the schema (e.g., it doesn't explain how 'variables' differ between CDK and Terraform implementations). The baseline score of 3 reflects adequate coverage through the schema alone.

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 tool's purpose: 'Deploys or destroys AWS infrastructure on LocalStack using CDK or Terraform.' It specifies the verb (deploy/destroy), resource (AWS infrastructure), and environment (LocalStack). However, it doesn't explicitly differentiate from sibling tools like 'localstack-aws-client' or 'localstack-management', which might also interact with LocalStack infrastructure.

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 usage context (CDK/Terraform/CloudFormation projects on LocalStack) but doesn't provide explicit guidance on when to use this tool versus alternatives like 'localstack-aws-client' for direct AWS API calls or 'localstack-management' for administrative tasks. No when-not-to-use scenarios or prerequisites are mentioned.

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