Assign Discord role

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it never mentions that this is a write requiring elevated permissions, that role hierarchy rules can cause failure, or what the 'confirm' flag does. With annotations present the bar is lower, but zero added context earns a 2.

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?

One short, front-loaded sentence with no filler, but this is under-specification rather than conciseness. The available budget is unused on information an agent genuinely needs for a permissioned mutation.

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 five-parameter permissioned mutation with an undocumented confirm gate, the description leaves out permissions, hierarchy constraints, idempotency behavior on repeat assignment, and parameter meaning. An output schema exists, so return values need not be explained, but the input side is entirely unaddressed.

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% across five parameters, and the description explains none of them. The 'confirm' boolean and 'reason' string (presumably the audit-log reason) are completely opaque, and the description does not even restate the required guildId/userId/roleId triple.

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 and resource: 'Assign a role to a guild member'. This is unambiguous and separable from siblings like discord_remove_role, discord_create_role, and discord_update_role. It does not explicitly name an alternative, so it stops short of a 5.

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 gives no when-to-use context, no prerequisites (e.g. Manage Roles permission, role hierarchy position), and no pointer to discord_remove_role as the inverse operation. The agent must infer all routing 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.