Update Team Member Role

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

Description adds behavioral context beyond annotations: authorization requirements (admins/owners only), a constraint (cannot change owner's role), and an idempotent hint from annotations is consistent. No contradictions with annotations.

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?

Description is concise with 3-4 sentences in English, plus a Spanish translation. No unnecessary information, though the Spanish repetition could be considered redundant in a bilingual context.

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 simple mutation with two parameters, the description covers purpose, authorization, constraints, and provides an example. Output schema exists, so return values are not required. Complete for the tool's complexity.

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?

Input schema already describes both parameters with 100% coverage. The description adds a concrete example (memberId='mbr_abc123', role='admin'), which provides practical usage context 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 'Change the role of an existing team member,' with a specific verb and resource. It distinguishes the tool from siblings like 'invite_team_member' and 'remove_team_member' by noting it does not change the owner's role.

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?

Explicitly states that only workspace admins or owners can change roles, and that the owner's role cannot be changed via this tool, directing users to a dedicated ownership transfer flow. This provides clear when-to-use and when-not-to-use guidance.

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