AWS MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers minimal details. It claims to list 'all' accounts without clarifying pagination behavior, whether suspended accounts are included, or that AWS Organizations is a global service (which affects how the region parameter behaves).

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 consists of a single, efficient sentence with no wasted words or boilerplate. It is appropriately front-loaded with the critical action and resource information.

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 read-only listing tool with a simple schema and no output schema provided, the description is minimally adequate. However, it omits what data is returned (account IDs, emails, status, ARN) and lacks important AWS Organizations context (e.g., that results may be paginated and require multiple API calls to get 'all').

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 description does not mention the profile or region parameters; however, the input schema has 100% description coverage with clear documentation including examples. With the schema providing complete semantic information, the baseline score of 3 is appropriate.

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 identifies the verb (List) and resource (AWS accounts in the organization), distinguishing it from sibling tools like aws_organizations_list_organizational_units or aws_organizations_list_roots that operate on different resource types. However, it lacks contextual guidance on the relationship between accounts and organizational units or when to prefer this tool over describe_organization.

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 no guidance on prerequisites (e.g., requiring Organizations master account or delegated admin permissions), no when-to-use versus alternatives, and no warnings about rate limiting or pagination. It states only what the tool does, not when to invoke it.

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