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

Goes well beyond the single destructiveHint=false annotation: discloses the auth requirement, a hard rate limit (50/day), the asynchronous outcome (invitation pending, not immediate membership), the consent flow ('对方接受与选择授权'), and the returned linkId used for viewing/revoking. Consistent with the non-destructive annotation since revocation is possible. Missing only edge cases such as duplicate or already-invited organizations.

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?

Single dense, front-loaded block that puts the login/permission requirement first, then prerequisites, then the action, rate limit, and side effects. No filler, though the bracketed tags and semicolon chaining make it slightly harder to scan than it needs to be.

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 3-param mutation with no output schema and minimal annotations, the description covers auth, rate limits, async semantics, the pending-consent model, and the return value (linkId). Enough for an agent to call it correctly; only duplicate/error handling and the linkId's use in cancel_alliance_invitation are left implicit.

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?

With 0% schema description coverage the description must carry the load, and it does: it names all three inputs conceptually (联盟 = allianceId, 组织 = organizationId, 邀请备注 = note) and frames the note as something to confirm beforehand. It adds no format or constraint detail beyond what the schema's maxLength/minLength already impose.

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 concrete verb+resource: sends a join invitation to an organization's managers so the organization joins the alliance. It also disambiguates directionality ('等待对方接受...不立即入盟'), distinguishing this inviter-side action from the apply/respond siblings, though it never names those tools explicitly.

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?

Prerequisites are explicit: login required and 'alliance manage' permission, plus a recommended prior step ('先查候选与工作台，确认联盟、组织及邀请备注') that maps to candidate-search and workbench siblings. It does not state when to prefer this over apply_organization_to_alliance or other invitation paths, so exclusions are absent.

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