discord_set_member_role

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is partly covered. The description adds meaningful context beyond them: the required Manage Roles permission and the role-hierarchy constraint. It does not describe side effects or audit-log behavior, but the auth requirements are a solid addition.

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, front-loaded sentences with no filler, and the core purpose leads. 'Returns: Confirmation.' is minimal and largely redundant given an output schema exists, which trims a point.

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?

With an output schema present the description need not explain return values, and annotations cover the mutation/idempotency profile. The permission and hierarchy prerequisites are the key operational detail an agent needs, so coverage is largely complete, with only the action/undo semantics left partly implicit.

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 60% (action and user_id are undocumented there). The description maps 'give a role / take it away' to the add/remove action enum and the role_id target, adding some meaning over the schema. But it says nothing about user_id or guild_id resolution, so it only partially compensates.

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 gives a specific verb and resource ('Give a role to a member, or take it away'), clearly stating that it manages member-role assignment rather than editing the role object itself. It is distinguishable from discord_edit_role/discord_delete_role, though it never names a sibling explicitly.

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 states the prerequisite permissions ('Needs Manage Roles, and the bot's own top role must sit above the role being assigned'), which is useful for deciding whether the call can succeed. However, it gives no when-to-use/when-not guidance and never points to an alternative tool.

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