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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the fallback behavior and bulk support, which is useful. However, it does not elaborate on what 'metadata' includes or any rate limits, but with annotations covering safety, this is acceptable.

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 extremely concise, with two sentences that are front-loaded with the primary purpose and then add two critical behavioral details (fallback and bulk support). No fluff, every word earns its place.

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 tool is relatively simple (read operation, no output schema), but it has 3 parameters and no schema descriptions. The description covers the fallback and bulk mode but does not explain the account parameter or return format. Given the simplicity, it is adequate but leaves gaps in parameter understanding.

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 0%, and there are 3 parameters with no descriptions in the schema. The description only mentions guild_ids for bulk support and implies guild_id for single, but does not explain account. With no schema details, the description should compensate but fails to define any parameter semantics beyond the bulk mention.

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 states the tool retrieves metadata for a single guild, which is a specific verb + resource. It differentiates from siblings by focusing on a single guild, unlike list_guilds. However, it doesn't fully clarify the difference from other get_* tools, though the resource is clear.

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 it is used when you need a single guild's metadata, and mentions fallback to default guild_id if not specified. It does not explicitly state when to use this over discord_get_guild_members or discord_list_guilds, but the single-guild focus is clear. No exclusions or alternatives are named.

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