get_payment_statusRead latest provider status for a customer payment attempt.
| Name | Required | Description | Default |
|---|---|---|---|
| attempt_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds modest value by specifying 'latest provider status', implying temporal freshness and an external provider source, but does not discuss error behavior or unknown attempt IDs. 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?
A single sentence that is front-loaded with the key verb and resource. Every word earns its place, and there is no filler or repetition of the schema.
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 a simple one-parameter tool, rich annotations, and an output schema that can document return fields, the description is nearly complete. It could add explicit guidance about invalid attempt IDs or the distinction from cancellation/retry, but it already provides enough for correct invocation in most cases.
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 0%, so the description must compensate for the undocumented attempt_id. It adds domain meaning by identifying the attempt as a 'customer payment attempt', but it does not explain where attempt_id comes from, how to format it, or what 'latest' means relative to retries. This is minimal but non-tautological compensation.
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 a specific verb ('Read'), a specific resource ('latest provider status'), and the scope ('a customer payment attempt'). This clearly distinguishes it from mutation siblings like retry_payment and cancel_payment_attempt, and from other reads like get_order or get_checkout_summary.
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 verb 'Read' provides clear context that this tool is for status retrieval, not for modifying or resuming a payment. It does not explicitly name alternatives or exclusions, but the purpose statement makes the intended usage obvious given the sibling tool names.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly separated by resource and action (cart, orders, tickets, picks, payments), so an agent can generally select the right one. The only notable ambiguity is resume_payment vs retry_payment, which both describe acting on an unpaid hosted payment attempt with nearly identical wording.
All 29 tools follow a consistent snake_case verb_noun (or verb_preposition_noun) pattern with standard verbs like get, list, create, close, remove, and set. There are no mixed conventions or vague generic names.
At 29 tools this is a heavy surface, but the broad e-commerce scope (catalog, cart, checkout, payment, orders, support, rewards) justifies most of them. A few payment-attempt tools could be consolidated, so it sits at the overbuilt rather than absurdly bloated end.
The set covers the main customer journey from browsing/searching sarees through cart, checkout, payment status, orders, and post-purchase support. Minor gaps exist—for example, no explicit apply_coupon/redeem_points tool or standalone catalogue listing—but agents can work around them with validate_coupon, checkout summary, and search.