Update Discord role

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, so the safety profile is covered structurally. The description adds only 'editable' and 'gradient colors' — it never explains that omitted fields are left unchanged (PATCH semantics), why a destructive hint coexists with idempotency, whether 'confirm' is required to proceed, or that changes are audited via 'reason'.

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?

A single short, front-loaded sentence with no filler — but its brevity is under-specification rather than efficiency, given the tool's 10-parameter surface.

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?

A destructive, idempotent mutation with a nested object parameter, 10 inputs, 0% schema description coverage and only 2 required fields. The description leaves the agent guessing about permission requirements, the confirm gate, and partial-update behavior; only the existence of an output schema spares it from a 1.

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 description coverage is 0% across 10 parameters, so the description must compensate and does not. It hints at the nested 'colors' object but says nothing about color vs. colors precedence, the format of 'permissions' (permission name strings), the role of 'confirm', or the 'reason' audit string.

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 (update Discord role fields) and adds scope ('editable' fields, gradient colors), which distinguishes it from create_role/delete_role siblings. It stops short of naming the read-only sibling discord_get_role or listing what is not editable.

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?

No when-to-use guidance, no prerequisites (e.g. MANAGE_ROLES permission), no mention of when to prefer discord_create_role or discord_assign_role. An agent must infer that this mutates an existing role identified by guildId/roleId.

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