discord_get_role

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

With no annotations provided, the description carries the full burden. 'Get details' clearly conveys a read-only operation with no destructive side effects. It doesn't explicitly state permissions, errors, or guild_id behavior, but for a simple retrieval operation the non-mutating behavior is transparent.

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 clear sentence with no filler. Every word is meaningful, and it is appropriately concise for a straightforward get-by-ID tool.

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?

The tool has an output schema, so return value details are covered elsewhere. However, the description is minimal for a 2-parameter tool with no schema descriptions; it doesn't clarify why guild_id is optional or when it should be provided, leaving a mild gap for correct invocation in ambiguous guild scenarios.

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 adds almost no parameter-level meaning beyond the object being a 'guild role.' It does not explain the relationship or necessity of role_id and guild_id, or how guild_id should be used, leaving the agent to infer parameter semantics from parameter names alone.

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 identifies the verb ('Get') and the resource ('details for a guild role') clearly, so an agent understands the operation is a read of one role. It distinguishes itself from sibling tools like discord_list_roles (all roles) and discord_get_role_permissions (permissions), though it doesn't explicitly contrast with them.

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 usage scenario is implied by 'Get' — use it when you need a specific role's details — but there is no explicit guidance on when to prefer this over discord_list_roles or discord_get_role_permissions. The description offers no exclusions or alternative routing.

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