list_aws_member_accounts

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

The description adds behavior beyond the `readOnlyHint`, `openWorldHint`, and `destructiveHint` annotations by explaining the pagination contract: pass the returned `pageToken`, and stop when no `pageToken` appears. It also discloses that the results include 30-day statistics and estimated monthly savings per savings/SP type.

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 compact and logically structured: purpose, return-value summary, then pagination instructions. The opening PerfectScale framing adds some non-essential context, but the description never wastes many words and stays easy to scan.

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 has no output schema, the description does a good job explaining the return content and pagination behavior. It is sufficient for an agent to successfully call the endpoint, though it relies on the parameter names and schema metadata for some fields like `maxResults` and `X-Tenant-Id`.

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 only 20%, so the description needed to compensate for the uncovered parameters. It adds useful semantics for `pageToken` and implies the role of `managementAccountId`, but it does not explain `maxResults`, `X-Tenant-Id`, or how `customerContext` should be used beyond the schema's existing description.

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 that the tool returns all member AWS accounts under an organization, specifically those with active or historical commitment coverage. This distinguishes it from sibling tools like `get_aws_member_account`, `list_aws_recommendations`, and `list_aws_planned_purchases`. The verb+resource+scope are all explicit.

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 gives clear operational context: use this to enumerate member AWS accounts that have commitment coverage, with 30-day statistics and savings data. It does not explicitly name alternatives or state when not to use this tool, so it stops just short of a 5.

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