refundStarPayment

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

No annotations are provided, so the description carries the behavioral disclosure burden. It states the precondition (only successful payments can be refunded) and the success result (returns True), which is useful. However, it does not disclose that a refund is irreversible, whether there are time limits or repeat-refund restrictions, or what happens on failure. For a financial mutation, this is thin but still minimally viable.

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 a single concise sentence that states the action and the return value with zero filler. It is front-loaded and every word earns its place.

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?

This is a simple two-parameter tool with no nested objects and no output schema, and the description does indicate the return value. However, with no annotations and no guidance about related tools or financial side effects, the definition is adequate but not fully complete for an agent operating autonomously.

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%, so the schema already explains both parameters. The description itself adds no extra parameter guidance beyond the tool-level context. The parameter descriptions are clear enough for the agent to understand what values are needed.

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 ('Refunds') and a precise resource ('a successful payment in Telegram Stars'). It clearly differentiates this from payment-creation tools like sendInvoice and read-only balance tools like getStarTransactions and getMyStarBalance, even with no title present.

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 implies the use case: refunding a Telegram Stars payment that was successful. However, it does not explicitly mention alternatives, such as using getStarTransactions to locate the charge ID, nor does it state when not to use this tool. The context is clear but no routing guidance is provided.

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