list_accountsList all configured AWS accounts and assumed roles to view your multi-account setup. Use this to identify available accounts for cross-account operations and dependency mapping.
List all configured AWS accounts (including assumed roles)
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only adds 'including assumed roles' and does not mention read-only nature, authentication requirements, scoping behavior, or failure characteristics.
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 sentence with no filler, and the key scope qualifier ('including assumed roles') is included up front. It is appropriately brief for a zero-parameter tool.
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 that there are no parameters and an output schema exists, the description is mostly complete for a simple listing operation. However, the large sibling list creates mild ambiguity about which account/profile listing tool to use, so a brief usage note would make it fully complete.
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 tool has zero parameters and the schema fully covers this with an empty properties object, so no parameter explanations are needed. The baseline of 4 applies because there is nothing for the description to add.
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 ('List') and resource ('all configured AWS accounts'), and adds the qualifier 'including assumed roles', which is concrete. However, it does not differentiate from the sibling tool list_profiles, so an agent might not know which 'list' tool to pick without further inspection.
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?
There is no guidance on when to use this tool versus list_profiles, get_account_info, or switch_account. The description implies a listing use case but offers no exclusions, alternatives, or context about when it is the appropriate choice.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.