get_payment_status

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

With no annotations provided, the description carries the full behavioral burden. It does not disclose whether the call is read-only/idempotent, what happens when the reference is unknown, what status values can be returned, or any auth/rate-limit constraints.

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 short sentence with the action and lookup key front-loaded and no wasted words. It is efficiently structured, though brevity here borders on under-specification rather than true conciseness.

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?

There is no output schema and no annotations, so the description should explain what a payment status response contains and what the possible statuses mean. As written, an agent cannot tell what it will receive back after a successful or failed lookup.

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% and the single parameter has no description, so the description must compensate. It only implies the parameter is a payment reference ('Ultraner reference') and gives no format, example, or validation detail, adding little beyond the schema's 'reference' field name.

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 ('Check') and resource ('payment') and identifies the lookup key ('Ultraner reference'), which is enough for an agent to understand the operation. It does not, however, differentiate itself from sibling readers such as list_transactions or get_wallet, so a weak but real clarity gap remains.

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?

There is no statement of when to use this tool versus list_transactions or the various create_* tools, and no mention of prerequisites. Usage is only implied by the verb 'Check'.

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