discord_list_roles

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

No annotations exist, so the description carries the burden of disclosing behavior. The word 'lists' indicates a read-only operation with no side effects, and 'with their properties' hints at the output structure. It lacks details on errors or permissions, but these are not critical for a basic listing tool.

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, concise sentence with no redundant words. It is well-structured and front-loaded with the main action and resource.

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?

There is no output schema, and the description only vaguely states 'with their properties' without specifying what those properties are or the format of the response. While an agent familiar with Discord might infer the standard role fields, the description leaves room for ambiguity and is not fully complete for a tool with no output schema.

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 input schema has one parameter, guildId, with no description. The tool description does not explain what guildId is, though it is reasonably inferable from the context of 'Discord server'. Since schema coverage is 0% and the description fails to clarify the parameter, it does not compensate for the missing schema details.

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) and the resource (roles in a Discord server) with their properties. It is distinct from sibling tools like create_role, edit_role, or assign_role, so an agent can easily identify when to use it.

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 implies usage for viewing server roles, and it is obviously a read-only operation. However, it does not explicitly contrast with alternative tools or state conditions for use, though the simple nature makes such guidance less necessary.

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