aws_list_key_pairs

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation by using 'List', but does not explicitly state behavioral traits like permissions, rate limits, or side effects. For a simple list operation, this is adequate but lacks extra context.

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?

Two sentences, no wasted words. The first states the action, the second provides valuable usage context. Every 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?

For a simple one-parameter list tool, the description is fairly complete. It explains purpose, region, and output usage. No output schema exists, but for a list tool, the return format is implicit. Minor gap: no mention of error conditions or edge cases, but overall sufficient.

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 coverage is 100% with one parameter 'region' described. The description does not add additional meaning beyond the schema, merely restating 'in the given region'. Baseline 3 applies as schema already documents the parameter.

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 lists EC2 key pairs in a given region, with a specific verb 'List' and resource 'EC2 key pairs'. It also explains the practical use of the returned key_name values, distinguishing it from other sibling tools like aws_run_instances.

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 for when to use the tool (to list key pairs) and explicitly ties the output to a related tool (aws_run_instances). It does not mention exclusions or alternatives, but none are necessary given the tool's specificity.

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