discord_get_server_info

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

No annotations are provided, so the description carries the full burden. It only states 'retrieves detailed information' without revealing the response format, error behavior, or permission requirements. The verb 'retrieves' implies read-only, but no further behavioral context is added.

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 sentence that immediately states the tool's action, with no filler or repetition. Every word contributes to the purpose.

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?

The description mentions two output elements (channels, member count) but calls the result 'detailed information' without further structure. There is no output schema, so the agent cannot anticipate the full return value, and prerequisites such as bot membership are not mentioned. For a simple one-parameter read, this is adequate but has clear gaps.

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 zero description for `guildId`, and the tool description does not explain that this ID is the Discord server ID or how to find it. With 0% schema coverage, the description fails to compensate, leaving the sole parameter ambiguous for an agent.

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 the specific verb 'retrieves' and identifies the resource as a 'Discord server', with concrete examples ('channels and member count'). This clearly differentiates it from siblings like discord_list_servers, which lists servers, and discord_get_forum_channels, which targets a specific channel type.

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 discord_list_servers for discovering server IDs, nor does it note any prerequisites or exclusion criteria, leaving the agent without decision support.

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