edgegate_change_member_role

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

With no annotations, the description carries the behavioral transparency burden. It discloses important non-obvious behaviors: the last-owner protection rule and the caller permission requirement. It does not describe return values or side effects, but for a role change tool these are the most critical behavioral traits and are well covered.

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 purpose. Every clause adds value: the main action, the critical exception, and the permission requirement. No filler or redundancy.

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 tool with 3 required params and no output schema, the description covers purpose, permission, and edge cases. It is complete enough for an agent to call it correctly in most scenarios, though it does not mention the success response format.

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 67% (user_id and role have descriptions). The description adds cross-parameter semantics: the 'cannot downgrade last owner' rule links user_id and role, and 'requires owner role' clarifies the caller's permission context. This goes beyond what the schema individually states.

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: 'Change a member's role in this workspace' — a specific verb, resource, and object. It is distinguishable from sibling tools like invite_member and remove_member, which handle adding/removing rather than changing roles.

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 clear context: it is used to change a member's role, and includes key preconditions (requires owner role) and an edge-case constraint (cannot downgrade the last owner). It does not explicitly name alternatives, but the purpose is unambiguous enough that an agent can infer when to use it.

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