discord_set_guild_locale

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

Annotations already declare it is a non-destructive, idempotent mutation with open-world scope, so the safety profile is covered. The description adds value beyond that by disclosing the permission requirement and stating that the previous and new locale are returned, useful for confirmation or rollback reasoning.

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 with zero waste: purpose and effect first, prerequisite and return value second. Everything is front-loaded and each clause 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?

With an output schema and rich annotations, the description covers the essentials: what changes, who can do it, and what comes back. Minor omissions like the audit-log 'reason' parameter and idempotency behavior are already handled by structured fields.

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 coverage is 100%, so guild_id, locale, and reason are fully documented in the schema; baseline 3 applies. The description adds conceptual meaning for locale (what it governs) but no syntax or format detail beyond the schema's example codes.

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?

States a specific verb and resource ('Set the server's preferred language') and immediately clarifies the scope of what that setting affects (Discord system messages and the default for members without one). This is distinguishable from siblings like discord_set_guild_name or discord_set_system_channel_notices without opening a schema.

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?

Provides the key prerequisite ('Requires Manage Server') and explains the effect context, which tells an agent when this is the right tool. It stops short of naming alternatives or stating when not to use it (e.g. that per-member locale is not changed here).

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