get_server_list

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the primary action and does not disclose any additional behavior like output format, pagination, permission requirements, or effects of the includeDetails parameter. The absence of any such detail makes it below average.

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, efficient sentence that directly states the tool's purpose. There is no redundancy or filler, and the key information is front-loaded.

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 list retrieval tool with one optional boolean parameter and no output schema, the minimal description is mostly sufficient. However, it lacks any mention of the response shape or that includeDetails modifies the output, which could help an agent, but the schema and purpose cover the essentials.

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 already has 100% coverage with a description for the includeDetails parameter. The tool description adds no parameter-specific meaning. Since schema documentation is complete, baseline of 3 applies.

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 fetches a list of Discord servers the bot is participating in, using a specific verb (取得) and resource (Discordサーバーの一覧). This distinguishes it from sibling tools like get_server_details, which is singular and implies a single server's details.

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 when a list of bot-joined servers is needed, but it doesn't explicitly mention when to prefer this over alternatives such as get_server_details or provide any explicit when-not-to-use guidance. It's minimally adequate but lacks clear contextual direction.

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