discord_get_roles

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

No annotations are provided, so the description must fully disclose behavioral traits. It states only 'list,' implying a read-only operation, but lacks details about permissions required, potential errors (e.g., invalid guild ID), rate limits, or the scope of roles returned (e.g., all roles in the guild).

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 very concise (5 words) and front-loaded, but it is too minimal. It could include a sentence about the return value or usage context without becoming verbose, so it is adequate but not optimal.

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 lack of annotations, output schema, and parameter descriptions, the tool definition is incomplete. The agent needs more context—such as what the return value contains, prerequisites, or how to handle errors—to use this tool effectively amid many sibling tools.

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 required parameter 'guildId' with no description in the schema (0% coverage) and no additional context in the tool description. The agent receives no guidance on how to obtain or use this parameter, reducing its ability to invoke the tool correctly.

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 'List a guild's roles' uses a specific verb (list) and clearly identifies the resource (roles). It succinctly defines the tool's function and distinguishes it from sibling tools like discord_add_role or discord_remove_role, which have different purposes.

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. It does not mention preconditions, such as having the guild ID, or contrast with other role-related operations like creating, editing, or deleting roles.

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