discord_upsert_role

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It discloses that role hierarchy limits manageability, which is useful, but it omits critical behaviors like the dryRun default (true) that would prevent actual changes, the semantics of roleId (present for update, absent for create), and any audit log or side effects.

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 exceptionally concise: two short sentences. The first states the core purpose; the second adds a relevant limitation. No redundant phrases. It is front-loaded with the action verb.

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?

For a tool with 5 parameters, a nested object schema, no output schema, and no annotations, the description is far from complete. It lacks any detail on request/response, dryRun semantics, or how to construct the body. It only provides a hint about role hierarchy, leaving major knowledge gaps.

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?

The schema offers no descriptions (0% coverage), and the description does not compensate. None of the parameters (guildId, body, roleId, dryRun, reason) are explained. The body parameter, an object with arbitrary properties, is completely opaque, leaving the agent with no understanding of what fields to supply.

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 uses a specific verb phrase 'Create or modify' with a concrete resource 'guild role,' clearly distinguishing the tool from siblings like 'discord_delete_role' and 'discord_reorder_roles.' The term 'upsert' is reinforced, making intent 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 provides no guidance on when to use this tool versus alternatives such as discord_delete_role or discord_reorder_roles. It only mentions a role hierarchy limitation, which is a constraint rather than usage direction. No when/when-not scenarios are given.

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