Select Profile

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 stateful action that affects subsequent operations, but does not disclose persistence, scope, side effects, or whether the selection applies globally or per request.

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?

A single sentence with no filler, front-loading the action and resource. It is appropriately brief, though the brevity shades into under-specification.

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?

Even though an output schema exists, the description leaves out important context: how selection affects subsequent commands, which sibling should be used for other profile-related tasks, and what values profile expects. Given multiple ambiguous siblings, this is not complete enough for reliable tool selection.

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 0%, and the description does not add meaning for the profile or region parameters. It does not clarify that region is optional or how profile values map to the listed profiles.

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 states a specific verb ('Select') and resource ('an AWS profile') with an intended purpose ('to use for operations'). It is clear and not a tautology, though it does not explicitly differentiate from similar siblings like assume_role or switch_account.

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 phrase 'to use for operations' hints at when it matters, but there is no guidance on when to choose this over alternatives such as switch_account, assume_role, or list_profiles. No exclusions or conditional context are provided.

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