get_payment_status

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

The annotation readOnlyHint=true already establishes that this is a safe, non-mutating read, so the description adds no safety context. Beyond that it says nothing about what statuses can be returned, whether the value is eventually consistent or cached, or any rate limits, leaving the behavioral profile bare.

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?

One front-loaded sentence with no filler or redundancy. It is efficient, though bordering on under-specification for the operation it describes.

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 one-parameter read tool with no output schema, the description should at least characterize the return (e.g., the set of status values) and its relation to get_payment. It is minimally viable but leaves a meaningful gap given there is no output schema to fall back on.

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% for the single payment_id parameter, so the schema already documents the input. The description adds no format, prefix, or source hints beyond what the schema provides, which is the baseline-3 case for fully covered params.

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 names a specific verb (Check) and resource (payment) with a stated scope (current status), so the operation is unambiguous. However, it gives no indication of how it differs from the sibling get_payment, which plausibly returns overlapping data, so the agent cannot distinguish them from the text alone.

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 guidance on when to use this tool instead of get_payment, list_payments, or get_off_cycle_payment, nor any stated prerequisites (e.g., whether the payment must be settled first). Usage must be inferred entirely from the name.

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