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

Annotations already declare this as a non-read-only, idempotent, non-destructive, closed-world mutation, but the description adds real behavioral context beyond them: human review, the two possible outcomes (credit refund or free-question restoration), the automatic no-charge policy for late answers, and the out-of-scope routing for monthly plans. This is exactly the kind of eligibility and process disclosure an agent needs.

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?

Four short sentences, front-loaded with the action and eligibility, then outcome, then auto-charge behavior, then plan-channel exclusion. No sentence is filler; each carries a distinct rule.

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 simple 3-parameter mutation with annotations and no output schema, the description covers eligibility, review process, refund outcomes, and out-of-scope cases thoroughly. The remaining gap is parameter-level: ticket_id and api_key are not defined anywhere, which an agent may need to call the tool 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?

Schema coverage is only 33%: reason is documented, but api_key and ticket_id are bare. The description partially compensates by implying ticket_id identifies the answer and the 7-day eligibility applies, but it never explains what ticket_id format is expected or what api_key represents. Partial compensation for a low-coverage schema.

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 and resource ('Requests a refund for an answer') plus an eligibility window, which immediately separates it from siblings like rate_answer, get_answer, and buy_credits. An agent knows exactly what this tool does without opening the schema.

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?

Gives explicit when-to-use ('within 7 days') and two when-not-to-use routes: late answers are auto-unbilled, and monthly plan refunds go through email. These are actionable exclusions and alternative channels, not vague hints.

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