list_aws_member_accounts

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

The annotations already mark the call as read-only and non-destructive, and the description enriches this by detailing pagination behavior ('call again passing the response's pageToken ... Stop once the response has no pageToken') and the returned information (30-day statistics, monthlyPotentialSavings per SP type). No contradiction with annotations.

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 main functional content is compact and the pagination advice is practical. The first sentence is promotional and not strictly necessary, but it does provide usage context, so the overall length is reasonable.

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?

Without an output schema, the description covers the core return values and the pagination protocol, and the schema covers parameter constraints. It omits some detail about X-Tenant-Id and response shape, but an agent has enough to call and consume the tool correctly.

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. It explains pageToken semantics and links managementAccountId to the 'specified AWS organization', but it leaves maxResults and X-Tenant-Id unexplained in either the schema or 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 states 'Returns all member AWS accounts under the specified AWS organization that have active or historical commitment coverage', providing a specific verb, resource, and scope. This clearly differentiates it from sibling tools like list_aws_savings_plans or get_aws_member_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?

It opens with a clear use-context: 'Evaluate current AWS commitments, plan and automate purchases, and optimize cloud costs with PerfectScale for Commitments'. It does not explicitly name alternatives or exclusion conditions, but it gives enough context for an agent to select this list tool over the many commitment/planning siblings.

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