discord_list_roles

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

No annotations are provided, so the description must carry the behavioral burden. 'List all roles in a guild' implies a non-destructive read operation, but it does not disclose any required permissions, potential size limits, or pagination behavior. The description adds no nuance beyond the obvious action, making it minimally adequate.

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 the core action front-loaded. There is no redundant information or unnecessary detail, 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?

For a simple listing tool, the description states the basic function, and the presence of an output schema presumably covers return details. However, it lacks any explanation of the optional 'guild_id' parameter and omits potential behavioral considerations (e.g., whether all roles are returned regardless of permissions). It is barely sufficient for an agent to use correctly.

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 a single optional parameter 'guild_id' with 0% description coverage. The description does not explain the purpose of this parameter, what happens when it is omitted, or how it relates to the 'guild' mentioned. With no schema documentation and no compensation in the description, the agent cannot infer the parameter's meaning.

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 action ('List'), the resource ('roles'), and the scope ('in a guild'), which distinguishes it from sibling tools like discord_get_role that target a specific role. It is unambiguous and specific.

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 provides no guidance on when to use this tool versus alternatives like discord_get_role or discord_analyze_server. It does not mention any conditions, prerequisites, or exclusions. The context of when to invoke this tool is left entirely to the agent's inference.

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