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

Annotations already declare destructiveHint=true, so the destructive nature is covered. The description adds a behavioral constraint: it only works on PENDING requests. This is a meaningful addition beyond the annotation, though it doesn't disclose potential errors or irreversibility details beyond what the annotation implies.

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, front-loaded sentence with no wasted words. It states the action and condition immediately, making it easy for an agent to parse quickly.

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 single-parameter cancellation with no output schema, the description covers the core purpose and condition. It doesn't mention error handling or response format, but given the low complexity and annotations covering destructiveness, it is mostly complete. A minor gap is not explaining what happens if the request is not in PENDING state, but that's an edge case.

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% (chargeRequestId is described as '충전 신청 ID'). The tool description adds no additional parameter context, so it does not exceed the baseline of 3 when the schema already documents the parameter.

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 a specific action (cancel) on a specific resource (charge request) with a condition (PENDING status). This distinguishes it from sibling tools like request_point_charge (create) and get_charge_request (read). The verb-resource pair is unambiguous.

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 a clear context for use: only when the charge request is in PENDING status. This implies the tool is not appropriate for non-pending requests, but it does not explicitly name alternatives or state exclusions. The condition is a useful guideline, though it doesn't contrast with other tools directly.

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