discord_server_info

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

With no annotations, the description carries the behavioral burden. 'Get detailed information' does indicate read-only disclosure, but the description does not cover the optional guild_id behavior, what 'detailed information' includes, or whether a default server is used when no id is supplied. It is not contradictory, just incomplete.

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 entire description is one focused sentence with no extra words, cliches, or redundancies. It immediately delivers the primary purpose and resource, making it highly usable and memorable.

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?

While the output schema partially reduces the need to document return values, the description does not cover the optional parameter's default, when to use this vs discord_analyze_server or discord_server_structure, and the operational context of 'server_info' relative to the broader Discord toolset. An agent might be able to invoke it, but not understand the most useful or intended calling pattern.

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 single guild_id parameter is never mentioned in the description, and schema description coverage is 0%. The description does not compensate for the parameter because it does not explain what guild_id means, whether a null default corresponds to a current/generic server, or how the agent should supply it for this call.

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 concrete verb ('Get') and a specific resource ('detailed information about a Discord guild/server'), clearly indicating this is a read/info tool. However, it is not explicitly differentiated from overlapping sibling tools like discord_analyze_server or discord_server_structure, so it loses the full 5.

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?

There is no guidance on when to prefer this tool over alternatives, no mention of prerequisites, and no exclusion criteria. Despite many sibling tools with similar informational purposes, the description gives the agent no navigation context.

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