List after-order payment options

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds a mobile-API access-token prerequisite and points to account_status/auth_start/auth_exchange as the required setup, which goes beyond the structured hints. Ends with 'Read-only', consistent with annotations. No contradiction.

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?

Four sentences, each with a distinct role: definition, usage, exclusion/alternative, and auth prerequisite. Slightly longer than minimal but no filler and front-loaded with the primary action.

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 output schema exists and annotations cover safety/idempotency, the description completes the picture: when to use, which sibling to avoid, what to pass, and what auth is required. Nothing essential is missing for an agent to call this 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 100% and both order_id and part_id are already documented as values from `order`. The description does not add syntax or additional meaning; it merely references passing a payment id to pay_after_order, which is about the next step rather than parameter semantics. Hence baseline 3.

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?

States a specific verb (List) and a resource (after-order payment options for an unpaid order part). Explicitly distinguishes from sibling web_pay_after_order by naming the mobile API path (getafterorderpayments) and from pay_after_order by saying the returned id is passed to it.

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?

Explicitly states when to use ('Use when the user has an unpaid order and wants to pay it through the mobile API'), names the excluded case ('Do not use for legacy web WCF orders'), and provides the alternative path (web_pay_after_order). Also gives prerequisite auth steps to determine readiness.

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