discord_set_guild_safety

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

Annotations already cover readOnly=false, idempotent=true, and destructive=false, but the description adds real value: auth needs (Manage Server), a concrete server-side rejection condition, partial-update behavior, and that applied values are returned. It omits that raising the verification level can lock out existing members, which is the main blast-radius concern for this mutation.

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?

Front-loaded with what the call changes, then constraints, then return behavior — four tight sentences with 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 present, the description needn't explain return values (it still notes them briefly), and with full schema coverage and annotations, everything an agent needs to invoke this correctly — permissions, conditional failure, partial-update behavior — is present.

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%, so every parameter including enums is already documented. The description restates the four settable fields and repeats the verification_level caveat that the schema also states, adding no new syntax or value semantics beyond the schema.

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 (Update) plus resource (server safety/moderation settings) and enumerates the exact four settings affected, so it is not confusable with discord_set_guild_channels or discord_update_membership_screening. It never names those adjacent siblings, so the differentiation is inferential rather than explicit.

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?

Gives the key operational rules: 'Only provided fields change' (partial-update semantics), 'Requires Manage Server' (prerequisite), and the verified/partnered requirement for high/very_high verification. It does not offer exclusions or name an alternative tool for related operations like AutoMod or membership screening.

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