list_billing_transfer_program_management_accounts

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral detail: pagination with pageToken, when to stop paginating, distributor-only access, and that handshake status is included. It doesn't fully describe the response shape, but for a read-only list this is reasonable.

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 pagination instructions are clear and the description is not overly long. However, the first sentence about 'Manage AWS billing-transfer mappings...' is broad, redundant with the listing focus, and could mislead. Some trimming would make it sharper.

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 simple paginated list tool with no required parameters, the description covers scope, returned content, and pagination. But with no output schema and multiple undocumented optional parameters, the description leaves gaps around the exact response format and the meaning of 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 25%, and the description compensates only for pageToken by explaining the pagination loop. maxResults and X-Tenant-Id remain unexplained, and customerContext is described only in the schema, not reinforced in the description. This is too little compensation for four parameters.

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 tool as a listing operation for the caller's program management accounts and reseller tenants, including handshake status. It distinguishes from sibling billing-transfer tools by focusing on PMAs and distributor scope, though the opening 'Manage AWS billing-transfer mappings' is broader than the actual read-only list and slightly muddies the purpose.

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 useful context by stating 'Distributor-only' and explaining pagination behavior. However, it does not explicitly say when to use this tool over sibling tools like list_billing_transfer_reseller_accounts_with_tenants or list_billing_transfer_end_customers, and it gives no exclusions beyond the distributor restriction.

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