discord_list_servers

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

With no annotations to signal side effects, the description itself conveys that this is a read-only listing operation scoped to the bot's memberships. It does not mention return format or potential edge cases, but the behavior is straightforward.

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, direct sentence with no unnecessary words. It fully names the action and scope without redundancy.

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 no-parameter listing tool, the description is sufficient for an agent to understand what will happen. It clearly states the scope (servers the bot belongs to) and that it returns all of them, so no further context is needed.

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 tool has zero parameters, so the description need not describe any inputs. The 0-params baseline applies, and no further parameter-level clarification is necessary.

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 ('Lists') and the resource ('all Discord servers the bot is a member of'), which is distinct from sibling tools like get_server_info that target a specific server.

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 makes the tool's scope clear but does not explicitly say when to use it versus alternatives. Given there is no direct sibling for listing all servers, the intended use is largely inferable, but explicit guidance is missing.

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