discord_list_servers

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

With no annotations, the description carries the full burden. It adds useful scope context ('the bot is a member of'), which constrains the results. However, it does not explicitly confirm that this is a read-only operation, nor does it describe any potential side effects, permissions required, or rate limits. For a simple list tool, this is adequate but not rich.

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, front-loaded sentence with no wasted words. It immediately states the action and scope, making it easy to parse.

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?

This is a low-complexity tool with no parameters, no annotations, and no output schema. The description conveys the core behavior clearly, but it does not specify the return format (e.g., server names, IDs, or objects). Given the simplicity, it is largely complete, but the lack of output schema detail prevents a perfect score.

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 zero parameters with 100% coverage trivially. The description adds no parameter-specific meaning because none exist. Baseline for 0 parameters is 4, which applies here.

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 uses a specific verb 'Lists' and identifies the resource 'all Discord servers the bot is a member of'. This clearly distinguishes it from sibling tools like discord_get_server_info (which targets a specific server) and discord_get_channel_list (which targets channels).

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?

No guidance is provided about when to use this tool versus alternatives. It does not mention that discord_get_server_info is better for specific server details or that this is the general inventorying tool. The description simply states the action without any contextual or alternative guidance.

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