List roles

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

The readOnlyHint annotation already declares the operation is read-only. The description adds valuable behavioral details beyond that: sorting order (highest first) and that permission bitfields are decoded to names, which informs the agent about the output format and processing.

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, well-structured sentence that front-loads the core action and adds useful details without any redundant wording. Every clause contributes meaningful information.

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 the simplicity of the tool (one parameter, read-only, no output schema), the description is adequately informative. It covers the scope, ordering, and a key output transformation. It does not mention potential edge cases like the @everyone role or pagination, but these are not critical for understanding the tool's function in this context.

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?

The schema has zero coverage for parameter descriptions, so the description must compensate. It mentions 'in a guild,' implying the guild_id parameter, but does not elaborate on its format or validate against the pattern. The parameter name is fairly self-explanatory, but the description does not fully bridge the gap left by missing schema descriptions.

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 states the exact action ('List every role in a guild'), specifies the order ('highest first'), and describes the output enrichment ('permission bitfields decoded to names'). This clearly distinguishes it from sibling tools like list_channels or get_guild.

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 context is clear: use this tool when you need a complete list of roles within a specific guild. However, it does not explicitly mention alternatives or when not to use it, but the purpose is self-evident from the description and tool name.

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