list_billing_transfer_reseller_accounts

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

Annotations already declare read-only and non-destructive behavior, so the bar is lower. The description adds context about returned fields (handshake state, status) and the scope (belonging to the calling reseller), which is useful. It does not cover pagination or authentication, but given the annotations, this is acceptable.

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 two sentences, but the first sentence is verbose and misleading (starts with 'Manage' when the tool lists). The second sentence is clear and front-loads the action, but the overall text could be tightened to remove the confusing start.

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?

No output schema exists, so the description is the only source of return information. It mentions handshake state and status but does not explain the response structure, pagination, or other fields. While the tool is a list operation, more detail about the output shape would improve completeness.

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 coverage is only 50% (X-Tenant-Id is undocumented) and the description provides no parameter guidance. It does not explain how to use customerContext or X-Tenant-Id, failing to compensate for the schema's incomplete parameter documentation.

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 the tool lists reseller program management accounts (RPMA) for the calling reseller, specifying the data included (handshake state and status) and explicitly excluding end-customer tenants. It also differentiates from similar tools by noting it is the reseller-tier analog of a specific GET endpoint, and contrasts with sibling tools like list_billing_transfer_reseller_accounts_with_tenants.

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 implies when to use this tool (when you need reseller accounts without tenants) by stating 'without end-customer tenants' and referencing an analog endpoint. However, it does not explicitly name alternative tools or provide direct when-not-to-use guidance, leaving the decision somewhat implicit.

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