share_handle_point_transfer

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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the risk profile is largely carried by structured data. The description adds real value with the 'confirm=true 执行' gate and the action values, but omits consequences (e.g. points irreversibly moved on accept, whether reject is reversible).

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?

Two short clauses, front-loaded with the action and followed by the execution gate; nothing is padded. Brevity is appropriate, though the terseness could arguably be at the expense of useful context.

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?

An output schema exists so return values need not be explained, and annotations cover destructiveness. However, for a mutating, destructive transfer-handling tool with no mention of auth prerequisites or what accept/reject actually does to the balance, the description leaves gaps an agent would want filled.

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 67% and the action enum has no schema description, so the description usefully supplies 'action=accept/reject' and clarifies that confirm=true is the executing flag. transfer_id is left entirely to the schema, so it neither fully compensates nor adds nothing.

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 ('accept or reject') and resource ('待处理转账' / pending transfer), which cleanly separates it from the create_ and list_ point-transfer siblings. It does not name those siblings explicitly, so it stops short of a 5.

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?

Usage is only implied: it operates on a 'pending transfer' with action=accept/reject, implying the transfer must already exist and be pending. No explicit when-to-use, when-not, or pointer to share_list_pending_point_transfers as the prerequisite step.

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