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

Annotations declare destructive, non-idempotent, open-world behavior; the description adds critical auth requirements (login, actual manager) and a scope limitation (pending only), which go beyond the annotations. It does not contradict them.

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 front-loads prerequisites (login, manager role) then the action and its scope. No wasted words.

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?

Given a destructive mutation with no output schema and 0% parameter description coverage, the description covers auth and scope well but leaves the two required parameters inadequately explained. An agent could still call it, but would need to infer parameter meanings.

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 0% and neither parameter is described in the schema. The description only instructs confirming the organization's linkId via a prior read; it provides no meaning or format for organizationId and only vague context for linkId, leaving parameter semantics largely unaddressed.

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 organization alliance application) and explicitly scopes it to pending applications only. This distinguishes it from sibling tools like leave_organization_alliance (exiting a joined alliance) and cancel_my_alliance_application (personal application).

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?

Specifies login requirement, actual manager role prerequisite, and a preparatory step (read alliance status and confirm linkId). Clearly states the tool only withdraws pending applications and does not exit joined alliances, though it does not name the alternative tool for exiting.

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