Suggest AWS CLI Commands

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

Annotations declare readOnlyHint=true, and the description confirms a read-only operation by describing the return as a dictionary of suggested commands. It adds transparency about the output structure, which annotations do not cover.

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 concise yet comprehensive: purpose, usage guidance, examples, and return description. Every sentence adds value, and the structure is front-loaded with the core function.

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 simplicity (single parameter, no nested objects, output schema mentioned), the description fully covers the purpose, usage, and behavior. Annotations and context signals do not leave gaps.

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 defines a single 'query' string parameter with examples. The description enriches this by advising on query formulation (include service name, action, context), which adds semantic guidance beyond the schema. Schema coverage is 100%, so the description lifts the baseline.

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 function: 'Suggest AWS CLI commands based on a natural language query.' It specifies the verb (suggest) and resource (AWS CLI commands), distinguishing it from sibling tools like call_aws (execution) and get_aws_regions (retrieval).

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 when to use this tool: when unsure about command syntax or exploring commands. It provides best practices for query formulation and includes examples. While it doesn't directly contrast with siblings, the implicit guidance is clear.

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