discord_create_role

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

The description adds value beyond annotations by specifying the permission requirement and that the new role is placed below the bot's highest role. Annotations already indicate mutation (readOnlyHint=false) and non-destructiveness, so the description supplements with context about side effects and constraints.

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?

Two sentences with no wasted words. The description is front-loaded with the main purpose and efficiently covers permissions, behavior, and a related sibling tool.

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?

Despite no output schema, the description states the return values (name and ID). It also covers the permission requirement and role positioning. Missing details like error handling or duplicate name behavior, but for a create tool with 6 parameters, the coverage is adequate.

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 100%, so the baseline is 3. The description does not add new parameter-level semantics beyond the schema's own descriptions, but it does not repeat them unnecessarily. A neutral score is 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?

The description clearly states 'Create a new role in a server' with a specific verb and resource. It distinguishes from siblings like discord_delete_role, discord_edit_role, and discord_add_role by mentioning the latter for assignment, making the tool's purpose unambiguous.

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?

Explicitly notes the required permission (Manage Roles) and the role positioning behavior. Provides a clear alternative for role assignment (discord_add_role), aiding the agent in deciding when to use this tool versus alternatives.

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