Update Discord guild settings

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is known. The description's added value is the backupId/allowWithoutBackup prerequisite, but it never explains what 'destructive' means here (guild-wide setting overwrite) or the role of the 'confirm' flag, leaving a meaningful gap for a mutation tool.

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 the field list first and the hard prerequisite second. Nothing is padded, though the second sentence could be clearer about it being a hard requirement versus a conditional one.

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?

Scored against the fact that an output schema exists (return values need not be described). Given annotations cover safety, the description supplies the one non-obvious operational constraint — the backup gate — plus the field surface. Combined with structured fields, an agent has enough to invoke it correctly.

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% across 12 parameters, so the description must compensate. It maps most fields loosely ('moderation levels', 'locale', 'AFK timeout') and covers backupId/allowWithoutBackup, but leaves guildId, reason, and confirm completely unexplained and never clarifies that 'moderation levels' spans verificationLevel, explicitContentFilter and defaultMessageNotifications.

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 ('Update basic guild settings') and enumerates the affected fields, which clearly separates it from update_channel/update_role siblings. It stops short of explicitly naming scope boundaries (e.g. guild-wide vs channel-level), but the guild-level framing is unambiguous.

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 supplies a real prerequisite — 'Requires a backupId or allowWithoutBackup' — which tells the agent a safety gate must be satisfied. It gives no guidance, however, on when to prefer this over backup_restore_apply or how to choose between backupId and allowWithoutBackup.

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