discord_admin_roles

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

The description merely restates the operation enum values from the schema (list, create, update, reorder, delete) and adds no behavioral context beyond what annotations already provide. It does not mention permissions, permanent deletion, side effects of reordering, or audit-log requirements, such as the 'reason' parameter. With destructiveHint=true already communicated, the description contributes little additional transparency.

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?

The description is a single concise sentence that front-loads the core actions. It contains no fluff or redundant detail, earning its place efficiently.

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 no output schema and only a terse description, the tool lacks crucial context for an agent: how to construct the 'data' payload, whether roleId is required for update/delete/reorder, what response format to expect, and additional behavioral side effects. The description is too minimal for a four-parameter tool with a destructive annotation and an open-world hint.

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 50% (data and reason have descriptions; roleId and operation lack them). The description names the operations but does not explain how roleId, data, or reason are used together, nor does it clarify the format of the 'data' request body. The operation parameter's enum already conveys the allowed values, so the description adds marginal semantic value.

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 identifies the tool's purpose: 'List, create, update, reorder, or delete server roles.' It uses specific verbs and the resource (server roles), and the sibling tools distinguish it from channels, members, messages, etc. This makes the tool's scope 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?

The description implies usage for role management but does not explicitly state when to choose this tool over alternatives like discord_admin_channels or discord_admin_request. There is no when-not-to-use guidance or mention of prerequisites, making the usage context clear only by inference from the resource name.

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