get_guild_info

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

With no annotations provided, the description must disclose behavior on its own. It states 'Get detailed information,' which implies a read-only operation, but it does not explain what 'detailed' includes, whether it performs a network call, returns cached data, or any potential side effects. The description is too sparse to provide meaningful behavioral transparency beyond the tool name's obvious semantics.

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, concise sentence that is front-loaded and contains no fluff. Every word contributes to the core meaning, making it highly efficient for a simple read operation.

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?

Despite having only one parameter and no annotations, the description lacks an output schema and does not specify what 'detailed information' encompasses (e.g., channels, roles, members). This leaves the agent uncertain about the return value and the tool's full capability, so it is not fully complete for a complex task.

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 only parameter, guild_id, already has a clear schema description ('Server ID'), and the description's use of 'Discord server' aligns with that. The description does not add extra meaning beyond the schema, but with 100% coverage, the baseline is 3, so this is appropriate.

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 ('Get') and a clear resource ('detailed information about a Discord server'), which directly maps to the tool name and distinguishes it from sibling tools like get_channel_info or get_user_info. It is unambiguous about what the tool returns.

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 is for retrieving detailed data about a specific server, but it does not explicitly state when to prefer this over alternatives like list_guilds or get_channel_info. There are no exclusions or comparative guidance, so the usage context is only implicit.

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