discord_assign_role

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

With no annotations provided, the description carries the full burden, but it only discloses the hierarchy-respecting behavior. It does not mention required permissions, failure modes, what happens if the member already has the role, or audit-log 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 a single, scannable sentence with no redundant wording. The core action is front-loaded, and the hierarchy constraint earns its place by conveying an important behavioral edge.

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 mutating Discord operation with no annotations, this is too thin. It omits the Manage Roles permission requirement, the role hierarchy failure condition, behavior for already-assigned roles, and guidance for the optional guild_id parameter.

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% and the description does not explain any parameters. The names member_id and role_id are reasonably self-evident, but reason and guild_id are left undocumented, and the description provides no guidance on how they relate to the operation.

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 and resource: assigning a role to a member, which is distinct from creating, editing, deleting, or removing roles. The phrase 'respecting hierarchy' adds a meaningful constraint that helps differentiate this from generic role manipulation.

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 this tool is for granting a role to a member, but it gives no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives like discord_remove_role or discord_set_role_permissions, so the agent must infer usage from the tool name alone.

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