Refund a JazzCash transaction

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

No annotations are provided, so the description bears full responsibility. It identifies a write operation (refund) and a permission requirement, but does not disclose failure modes, idempotency, rate limits, or return behavior.

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?

The description is two sentences, front-loaded with the core action, and free of fluff. However, it could be slightly more structured by listing the parameters or conditions.

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?

Without an output schema or annotations, the description must cover prerequisites, behavior, and results. It mentions permissions but omits error handling, success response, and fails to describe the three required parameters.

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?

With 0% schema description coverage and no parameter descriptions in the text, the agent receives no explanation for txn_ref_no, amount_paisa, or description. The description's mention of 'full or partial refund' loosely connects to amount but does not clarify units or identifiers.

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 clearly states the tool issues a refund, specifies it can be full or partial, and targets previously settled JazzCash transactions. This distinguishes it from sibling tools like charge, checkout, or inquiry.

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?

It provides context (settled transaction) and a prerequisite (refund permissions enabled), but lacks explicit guidance on when not to use or alternatives. The agent can infer usage, but no exclusions are stated.

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