update_workspace_member_role

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

With no annotations, the description must disclose all behavioral traits. It mentions 'Effective immediately' and clarifies no effect on org role or other workspaces. However, it omits details on permissions, error handling, reversibility, and the purpose of the 'confirm' parameter, which is a safety mechanism.

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 three sentences, front-loaded with the core action, followed by immediate effect and scope limitations. No superfluous information.

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?

The description covers the main purpose and key behavioral aspects. However, it omits explanation of the 'confirm' parameter (a non-obvious requirement), permission prerequisites, and what happens on failure. With an output schema present (not shown), return values are less critical. Overall adequate but could be enriched.

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 50% (2 of 4 params have descriptions). The tool description does not add any parameter-level detail beyond what the schema provides. For instance, it does not explain what workspace_id or user_id represent. Given moderate coverage, description should compensate but fails to do so.

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 'Change a member's role within a workspace,' specifying the verb (change) and resource (member's role). It distinguishes from siblings like 'update_member_role' by noting it does not affect org-level role, implying a separate tool for org roles. The differentiation is effective.

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 provides context by stating the change is workspace-specific and does not affect org-level role, guiding the agent to use this for workspace roles. However, it does not explicitly name alternative tools or state when not to use it.

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