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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known. The description adds substantive context beyond that: login is required, alliance 'manage' permission is needed, and the effect is limited to pending invitations without ejecting joined orgs.

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?

A single compact sentence with the auth requirement front-loaded and the scoping constraint appended. No filler, though the bracketed login tag and permission clause make it slightly dense.

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 2-param destructive action with no output schema, it covers access prerequisites, the verification step, and the effect boundary. The main omission is a concrete explanation of the linkId/allianceId parameters.

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 0% for the two required params, so the description carries the burden. It references linkId by name (核实 linkId 与组织) and implies the organization context, but never explains what linkId identifies or how allianceId relates, leaving the compensation incomplete.

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 (撤回联盟发出的加盟邀请 / withdraw an alliance invitation) and draws a clear boundary: it only cancels pending invitations and does not remove already-joined organizations. This distinguishes it from sibling mutators like detach_alliance_organization and remove_organization_member without needing their names.

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 the precondition (【需要登录】須联盟 manage) and the negative scope (只取消待接受邀请，不移出已加盟组织), which tells the agent when NOT to reach for this tool. It stops short of naming a direct alternative to use for removal, but the routing context is clear.

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