discord_get_guild_info

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's 'Read-only' merely restates that. Beyond the annotation, the description adds the shape of the returned metadata, but with an output schema present that content is largely redundant rather than new behavioral context (no rate limits, permission requirements, or failure modes).

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?

Two tight sentences: the capability and its return fields are front-loaded, followed by the disambiguation pointer. No filler or repetition.

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?

With an output schema covering return values, annotations covering the safety profile, and a fully documented single parameter, the definition is nearly complete. The only gap is operational context (bot-membership/permission requirements for reading a guild), which an agent would need in edge cases.

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?

Schema description coverage is 100% and the single guild_id parameter is fully documented as a snowflake with a pattern constraint. The description adds no further meaning about the identifier (e.g., where to obtain it), so the baseline 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?

Names a specific verb (Get) and resource (details about one server) and enumerates exactly which fields come back (name, description, counts, boost tier, owner, creation date). This is clearly distinguishable from the stats-oriented sibling it names.

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?

Explicitly routes the agent to discord_get_server_stats for a finer breakdown (humans vs bots, channel types), which is real when-to-use guidance. It stops short of covering the other obvious alternative, discord_list_guilds, and gives no prerequisites such as the bot needing to be in the guild.

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