Execute AWS CLI Command

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

Annotations already indicate destructiveHint=true, so destructive potential is known. The description adds behavioral context: default region (us-east-1), working directory, and file path requirements. It also states validation and error handling are present. The description does not contradict annotations (no annotation_contradiction). Some additional detail about what could be destroyed (e.g., data operations) would be beneficial, but overall it's adequate.

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 well-organized with sections for key points, command restrictions, examples, and return info. Every sentence adds meaningful guidance without redundancy. It is front-loaded with the core purpose and usage instructions. At approximately 150 words, it is appropriately sized for the tool's complexity.

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), the description covers essential operational constraints (syntax, restrictions, working directory, default region) and provides multiple examples. The presence of an output schema (not shown but confirmed in context) reduces the need to detail return values, though the description gives a high-level summary. The description is sufficiently complete for an agent to use the tool 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?

Schema description coverage is 100% (both cli_command and max_results have descriptions). The description adds value beyond schema by emphasizing that cli_command must start with 'aws', providing usage examples, and clarifying that max_results is for pagination. The schema alone would not convey these usage constraints.

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 executes AWS CLI commands with validation and error handling. It distinguishes itself from siblings like 'suggest_aws_commands' which suggests commands, and 'get_aws_regions' or 'get_caller_identity' which retrieve specific data. The verb 'Execute' plus resource 'AWS CLI commands' is specific and unambiguous.

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 says to use this tool when you know the specific AWS service and operation, and provides a list of restrictions (no pipes, redirects, shell variables) and required syntax (command must start with 'aws'). Examples illustrate proper usage. It does not explicitly contrast with sibling tools for when not to use, but the guidance is clear enough for an agent.

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