discord_add_role

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: it's a mutation operation (implied by 'Add'), requires specific permissions ('Manage Roles'), and has a hierarchical constraint ('target role must be below the bot's highest role'). However, it doesn't mention rate limits, error conditions, or response format, leaving some gaps.

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 front-loaded with the core purpose in the first clause, followed by essential prerequisites. Both sentences earn their place by providing critical information without redundancy or fluff, making it highly efficient.

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?

Given no annotations, no output schema, and 0% schema description coverage for a 4-parameter mutation tool, the description is moderately complete. It covers purpose, usage context, and key constraints, but lacks details on parameter semantics, return values, error handling, or side effects, which are important for a tool with permissions and hierarchical rules.

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%, so the description must compensate for undocumented parameters. It implicitly references guild_id, user_id, and role_id through context ('guild member', 'role'), but doesn't explain parameter meanings, formats, or the optional 'reason' parameter. The description adds minimal semantic value beyond what's inferable from parameter names.

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 the specific action ('Add a role') and target ('to a guild member'), distinguishing it from sibling tools like discord_remove_role, discord_list_roles, or discord_kick_user. It precisely identifies the verb and resource without ambiguity.

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 explicitly states when to use this tool ('Add a role to a guild member') and provides critical prerequisites: 'Requires Manage Roles and the target role must be below the bot's highest role.' This gives clear context for usage versus alternatives like discord_remove_role or other member management tools.

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