بررسی وضعیت پرداخت در TheyPaid

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

With no annotations, the description carries the full disclosure burden. It usefully reveals that the status is fetched fresh from TheyPaid and that a PAID response is required before confirming, plus that expected asset/amount are cross-checked — but it omits what happens on mismatch, whether mismatches raise errors or return a flag, and what the tool returns.

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?

Three tight sentences with the action front-loaded and no filler; the confirmation rule follows immediately. Slight deduction because the middle sentence about confirmation and the last about comparison could be merged without loss.

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 3-parameter read tool with no annotations and no output schema, the description covers purpose and the PAID confirmation rule but not the return shape (status values beyond PAID, mismatch outcome) or error behavior. Adequate but with clear gaps an agent would hit on first invocation.

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. It does explain the two optional parameters semantically: if expectedAssetId/expectedAmountInTether are supplied, they are compared against the invoice. However, it leaves the consequence of a failed comparison unspecified, and invoiceId is only implicitly covered by the tool's purpose.

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 first sentence states a concrete verb+resource: it re-reads invoice status from TheyPaid, and it adds the confirmation rule (only PAID counts). However, it never distinguishes itself from sibling tools like theypaid_get_invoice, theypaid_recheck_invoice, or theypaid_wait_for_payment, which an agent could easily confuse with this one.

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 gives a decision rule ('only declare the payment confirmed when the response is PAID'), which implies this is a verification call. But it offers no explicit guidance on when to choose this over recheck_invoice, get_invoice, or wait_for_payment, nor whether it should be polled repeatedly or called once.

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