discord_create_role

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

Annotations cover the safety profile (not read-only, not destructive, not idempotent, open-world), and the description adds value beyond them: the Manage Roles authorization requirement and the behavioral note that new roles land at the bottom of the hierarchy. It doesn't cover error cases such as hitting the role limit, so it stops short of 5.

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 padding; purpose comes first, then prerequisites, then hierarchy behavior. The 'Returns: Confirmation with the role ID' line is mildly redundant given an output schema exists, keeping it from a 5.

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 and annotations present, the description is complete enough: purpose, auth requirement, and a key behavioral trait are all stated. Minor gaps remain around failure modes (permission errors, role limits) for a 7-parameter mutation tool.

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 86%, so the schema already documents the parameters (color format, hoist, mentionable, permissions bitfield, guild_id fallback). The description adds no parameter detail, making the baseline 3 appropriate.

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 ('Create a role') that inherently separates it from discord_edit_role, discord_delete_role, and discord_list_roles. It stops short of naming a sibling explicitly, so it's clear but not maximally differentiated.

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?

'Needs Manage Roles' gives a permission prerequisite, which is genuine usage context, but there is no explicit when-to-use, when-not-to-use, or routing to alternatives like discord_edit_role for later changes. Usage is only implied.

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