update_space_member_role

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

With readOnlyHint=false and destructiveHint=false already present, the description adds no behavioral context beyond what annotations provide. It does not explain whether this is an overwrite, whether it requires special permissions, or whether the change can be reverted. No contradiction exists, but the description carries little additional transparency burden.

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 clear sentence with no filler or redundant wording. It is front-loaded with the action and resource. Conciseness is excellent, though this does not compensate for missing semantic guidance.

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 low schema coverage, no output schema, and no usage guidance, the description is incomplete for safe and correct invocation. An agent cannot determine how to specify a member versus a group, whether one of user_id/group_id is required, or what the result/effects of the change will be. The description only provides the basic purpose.

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?

The schema has only 25% parameter description coverage, and the description does not compensate. It says the target can be a member or group, which loosely maps to user_id and group_id, but it does not clarify that exactly one of these should be provided, nor does it explain the relationship to the required space_id and role. The enum on role is already structured in the schema, so the description adds minimal parameter-level value.

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 'Change a space member or group's role.' clearly states the action (change), the resource (space member/group), and the attribute affected (role). It is specific enough to distinguish from the sibling tools like add_space_members or remove_space_member, though it does not explicitly name an alternative.

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 gives no explicit guidance about when to use this tool versus add_space_members, remove_space_member, or update_space. There is no mention of prerequisites, such as the need to provide either user_id or group_id, or any exclusions. Usage is only weakly implied by the phrase 'change ... role'.

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