localstack-aws-client

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

The description adds useful context beyond annotations (e.g., it runs against a LocalStack container using 'awslocal'), but annotations are minimal (only a title), so the description carries more burden. It does not disclose behavioral traits like error handling, rate limits, or authentication needs, which are relevant for a command execution tool.

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 is front-loaded with the core purpose and includes essential details (e.g., 'awslocal' wrapper) without any wasted words, making it highly concise and well-structured.

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 (executing arbitrary AWS CLI commands), lack of output schema, and minimal annotations, the description is adequate but incomplete. It does not explain return values, error cases, or execution constraints, which are important for an agent to use it correctly in varied contexts.

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 description coverage is 100%, so the schema already documents the 'command' parameter thoroughly. The description adds minimal value by clarifying not to include 'awslocal' or 'aws' in the command, but this is a minor enhancement beyond the schema's details.

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 with specific verbs ('executes') and resources ('AWS CLI command against the running LocalStack container'), and it distinguishes itself from siblings by specifying the 'awslocal' wrapper, which is unique to this tool among the listed siblings.

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 provides clear context on when to use this tool (for AWS CLI commands against LocalStack) and implicitly distinguishes it from alternatives by mentioning the 'awslocal' wrapper, but it does not explicitly state when not to use it or name specific alternative tools for comparison.

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