درخواست بررسی دوبارهٔ فاکتور

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

No annotations are provided, so the description carries the whole burden. 'اجرا' (execute/run) implies a server-side action beyond a pure read, but it does not say whether this mutates invoice state, whether it hits the payment provider, whether it costs credit or is rate-limited, or whether it is synchronous or long-running. The only behavioral disclosure is that it returns the 'latest recorded status'.

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 compact sentence with the action front-loaded and the return behavior appended — no filler. It is arguably too terse rather than bloated, but structurally it is sound.

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 must cover both input sourcing and return shape; it only gestures at 'latest recorded status' without saying what that status contains or how it differs from a plain get. For a recheck operation with possible side effects, that leaves key questions unanswered.

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 invoiceId has only pattern/length constraints, with no explanation of where the ID comes from or what form it takes. The description never mentions invoiceId, so it adds nothing over the schema for the one required input.

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 (recheck / بررسی دوباره) on a specific resource (invoice / فاکتور) and adds that it returns the latest recorded status. It does not, however, distinguish itself from close siblings such as theypaid_get_invoice, theypaid_check_payment, or theypaid_wait_for_payment, so an agent still has to infer why it would recheck rather than simply fetch.

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 offers no when-to-use or when-not-to-use guidance and names no alternative. It never says whether to call this instead of theypaid_get_invoice when a status looks stale, nor whether it should follow theypaid_check_payment or theypaid_wait_for_payment — the choice is left entirely to the tool name.

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