List Discord roles

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

No annotations exist, so the description carries the burden. It indicates a listing operation (read-only) but doesn't explicitly state that, nor does it mention any side effects or requirements. It does say 'so a name the user said can be matched to one' which implies usage context but not full behavioral transparency about errors or return.

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 one sentence, concise, and front-loaded with the action. It delivers the essential purpose without fluff.

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 there is no output schema)Skip, the description explains what is listed and why. It provides enough context for a typical use case. It doesn't mention return format, but that is often inferred.

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 already describes the parameter as 'Game name or universe id.' The tool description doesn't add new semantics beyond the schema, but it does connect it to the context of listing Discord roles. With 100% coverage, baseline is 3.

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 tool's function: listing Discord roles that can be notified, with a specific use case of matching a user-said name to a role. This is more specific than generic 'list roles' and gives context.

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 when to use it (when needing to match a user-said name to a role) but does not explicitly state prerequisites or typical invocation context. It's adequate but lacks explicit guidance like 'call this before sending a notification'.

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