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

With only readOnlyHint=false in annotations, the description adds meaningful behavioral context: role hierarchy, non-assignable owner, no guest, and the actor-tier permission rule. It does not describe response behavior, error cases, or audit effects, but the permission model is unusually well disclosed.

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 compact sentences with the core action first, followed by role ranking and the authorization rule. Every sentence contributes directly to correct invocation.

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 three-parameter mutation tool with full schema coverage and no output schema, the description supplies the invocation-critical permission and role-hierarchy details. It leaves some minor gaps around return values and whether the target must already be a member.

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 the schema already explains all three parameters. The description still adds useful meaning by giving numeric role tiers and clarifying that an actor can assign roles below their own tier, though the relationship to the schema's 'up to one tier below' wording could be clearer.

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 names the specific action (promote/demote a member) and the resource (member role), and gives the role hierarchy. It clearly distinguishes role assignment from adjacent tools like kick, ban, or update.

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?

It provides the key authorization context: an actor may assign any role below their own tier, and gives the superadmin-to-admin example. It also excludes 'guest' and implies owner is not assignable, but it does not explicitly name alternatives or when not to use this tool.

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