appflowy_update_member

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only states that the tool updates role or name, without any mention of side effects, authorization requirements, rate limits, or what happens on failure. This is minimal disclosure for a mutation tool.

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 a single concise sentence that front-loads the key action. It is efficient but could benefit from expanding on parameter details without becoming verbose.

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's complexity (nested object, no output schema, no annotations), the description is incomplete. It does not explain how to identify the member (email required), what workspace_id means, or what the expected return value or error conditions are. Significant gaps remain.

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 explain all parameters. It partially covers 'role' (with enum values) and 'name', but omits 'workspace_id' (what it identifies) and 'email' (required in request object but not mentioned in description). This leaves key parameters unexplained.

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 verb 'Update', the resource 'workspace member', and the specific fields that can be updated (role with enumerated values, name). It distinguishes this tool from siblings like appflowy_invite_members and appflowy_remove_members by specifying the update action.

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?

The description implies the tool is for updating member roles or names but does not provide explicit guidance on when to use vs alternatives (e.g., invite, remove) or mention prerequisites like user permissions or workspace membership. Usage context is left to inference.

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