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

Adds substantial context beyond the annotations: login required, alliance manage permission needed, a hard rate limit of 50/day, the async nature (waits for recipient to accept and choose authorization), and the return value linkId for viewing/withdrawing. Annotations only cover the generic mutation profile; the description supplies the operation-specific behavior.

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 dense sentence pack, front-loaded with the login/permission gate and then the workflow, rate limit, async behavior, and return. No wasted text, though the stacking of clauses slightly reduces scannability.

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 non-idempotent, non-destructive mutation with no output schema, the description covers auth requirements, prerequisites, rate limits, the deferred/async outcome, and the returned linkId. Nothing an agent needs to invoke it correctly is missing.

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%, so the description must carry the burden, and it conceptually maps all three params (联盟=allianceId, 组织=organizationId, 邀请备注=note). However, it adds no format, length, or source details for these IDs beyond naming the concepts.

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: sending a join (加盟) invitation to an organization's manager. It clearly positions the tool as an outbound invitation flow, distinguishable from the reversed sibling apply_organization_to_alliance and from invite_organization_members.

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 prerequisites: '先查候选与工作台，确认联盟、组织及邀请备注' — check candidates and workbench, confirm alliance, organization and note before sending. It also explains the outcome ('不立即入盟' — not immediate membership). It stops short of naming a specific alternative tool to use instead.

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