refund_star_payment

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

Annotations already disclose that this is a non-read-only, non-destructive, and idempotent operation. The description adds no additional behavioral context such as refund limits, timing constraints, or side effects, failing to go beyond the structured data.

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 one short sentence, well front-loaded with the action and target. It is efficient, though so terse that it borders on under-specification rather than polished brevity.

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 tool with two required parameters and no output schema, the description is incomplete: it does not explain the meaning of the parameters, any prerequisites, or expected outcomes. The brief statement covers only the high-level action, leaving the agent without enough information to use it correctly.

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, the description should compensate for lack of parameter documentation, but it does not. The param names 'user_id' and 'telegram_payment_charge_id' are somewhat self-explanatory, yet no guidance is given on what values to provide or where to obtain them.

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 uses a specific verb ('Refund') and a clear resource ('Telegram Star payment'), making the tool's function immediately obvious. It distinguishes itself from sibling payment-related tools like get_star_transactions or get_my_star_balance by indicating a mutating operation.

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 provides no guidance on when to use this tool, prerequisites, or alternatives. It simply states the operation without any context on eligibility conditions or relationships to other payment tools.

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