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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent mutation. The description adds one genuinely new behavioral detail — 'Действует сразу' (takes effect immediately) — but omits what happens to prior permissions, whether the member is notified, or any permission prerequisites.

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?

Three short sentences, front-loaded with the core action and effect. No filler, though the parenthetical role-source note partly repeats the schema.

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 3-param mutation tool with full annotation coverage and no output schema, the description covers what changes, that it applies immediately, and where the role comes from. Adequate, with only minor gaps around permissions and notification side-effects.

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 all three params are already documented in the schema (including the get_workspace_roles source). The description's mention of the role source duplicates rather than extends the schema, landing at the baseline 3.

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 ('Меняет роль участника') and clarifies the effect ('то, что он может делать в аккаунте'), which separates it from sibling tools like remove_workspace_member and invite_workspace_member. However, it does not explicitly distinguish itself from set_workspace_member_folders, so differentiation is only implied.

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 points to where the role_id comes from ('из get_workspace_roles'), which is useful context, but gives no explicit when-to-use vs when-not guidance and no alternatives. Usage is only implied from the verb.

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