discord_get_role_permissions

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

There are no annotations, so the description carries the full burden of behavioral transparency. It implies a read operation, but does not disclose permission requirements, what happens with the optional guild_id, or whether the bitfield is the raw stored value versus an effective computed permission set.

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 one tight, front-loaded sentence. It contains no filler and earns its place.

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?

An output schema likely covers the return values, so the brief description is partially sufficient. However, the optional guild_id parameter and the implications of role permission bitfields versus effective permissions are missing, making the definition minimally viable but incomplete.

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?

With 0% schema description coverage, the description needed to explain both parameters; instead it adds little beyond the role_id concept. The optional guild_id is left completely unexplained, including when it is needed and what the null default means.

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 has a specific verb, 'Get', and a clear resource, 'permission bitfield and flags for a role'. It distinguishes the tool from generic role retrieval, but does not explicitly clarify how it differs from discord_get_role or discord_get_member_permissions.

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?

No guidance is provided for when to choose this tool over alternatives such as discord_get_role, discord_get_member_permissions, or discord_set_role_permissions. The agent must infer the correct context from the name alone.

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