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

Beyond the annotations (destructive=true, idempotent=false), the description discloses that removal revokes ALL alliance stationing access, that the affected person is notified, that the leader is protected, and that validation is centralized in the alliance service. These are non-obvious side effects an agent needs before invoking a destructive mutation.

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?

It is a dense but front-loaded paragraph that opens with the login and permission requirements, and almost every clause earns its place (rules, workflow, notification, param meaning, alternative). Slightly overpacked and could be split for scanability.

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 two-parameter destructive mutation with no output schema, the description covers permissions, protective rules, the required pre-call verification, the access revocation side effect, the notification, and the self-exit alternative. Nothing essential 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 coverage is 0%, so the description must carry the burden. It usefully clarifies that userId is the person's id rather than the membership-relation id, but it leaves allianceId unexplained and confusingly references an organizationId parameter that does not exist on this tool, which could mislead.

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?

The description names a specific verb+resource (removing an alliance member) and immediately distinguishes it from the self-exit sibling by pointing to leave_organization. An agent can tell this apart from remove_organization_member and leave_organization_alliance without opening any schema.

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?

It gives explicit preconditions (login + alliance management capability, admin removal requires the leader, leader cannot be removed), directs the agent to call get_alliance_workbench first to verify the person and role, and names the alternative leave_organization for self-exit with its id source. This is nearly complete when/when-not guidance.

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