appflowy_remove_members

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

The description only states 'Remove', implying destructive action, but with no annotations, it fails to disclose whether removal is irreversible, whether it requires specific permissions, or whether it triggers notifications. A mutation tool should provide more behavioral context.

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?

The description is concise (one sentence, no fluff) but is under-specified. It sacrifices necessary detail for brevity, making it minimally viable but not well-structured for an agent. A slightly expanded description would improve utility.

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 the tool has two required parameters, no output schema, and no annotations, the description is too brief to be considered complete. It omits information about success behavior, error cases, idempotency, and response format, which are important for an agent to use the tool correctly.

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 compensate. It adds minimal value by hinting that 'emails' is used for identification, but it does not explain the role of 'workspace_id' or that 'emails' is an array. The description is too vague to help the agent understand parameter semantics beyond the schema.

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 clearly states the action ('Remove members') and the resource ('from a workspace') and the method ('by email'). It distinguishes from sibling tools like invite, list, and update. However, it does not explicitly mention that multiple members can be removed via an array of emails, which is implied by the input 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?

No guidance is provided on when to use this tool versus alternatives (e.g., appflowy_update_member for changing role, appflowy_invite_members for adding). It also lacks prerequisites (e.g., admin permissions) or conditions where removal is not allowed.

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