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

Goes well beyond annotations (which only flag destructive/idempotent): discloses the admin authorization requirement, the partial-update rule, and the concrete side effect that downgrades immediately reconcile task holds and browser views. That is exactly the consequence context an agent needs before a destructive write.

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?

Two sentences, front-loaded with the core action and the omit-is-kept rule, then the parameter addressing rules, prerequisites, and side effects. Dense but every clause carries information; minor cost is that the second sentence packs three distinct ideas.

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?

Output schema exists and annotations cover safety, so the description only needs authorization, mutation semantics, and addressing rules — all present. Only gap is the absence of explicit routing to sibling tools (add/remove/team equivalents).

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 100%, so the baseline is 3, but the description adds real cross-tool meaning: 'member' is the row id from workspace_member_list and stands alone, or an account id/alias/email when paired with workspaceId. It also restates the omission-keeps-current behavior for role and membership.

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+resource ('Change a member's role, membership ... or both') and clarifies update-vs-replace semantics with 'what you omit is kept'. The 'workspace member' scope implicitly separates it from team_set_member_role and workspace_member_add, but no sibling is named explicitly.

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?

Provides the key prerequisite ('Workspace administrators only') and implies this is the modify-existing-member tool rather than the add path, but never names workspace_member_add or team_set_member_role as alternatives, or states when a caller should re-invite instead of changing role.

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