discord_set_system_channel_notices

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

Beyond annotations (readOnly=false, idempotent=true, destructive=false, openWorld=true) the description adds three genuinely useful facts: the Manage Server permission requirement, the partial-update semantics ("Only provided flags change"), and that the resulting flag set is returned. What it does not say is whether omitting a flag leaves it untouched on the system channel or how the change is audited, though the audit-log `reason` param covers part of that.

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?

Three tight sentences: scope first, mutation semantics second, permission/return last. Zero redundancy and nothing buried.

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?

An output schema exists and the input schema is fully documented; combined with the enumerated flags, permission requirement, and partial-update rule, an agent has everything needed to invoke this correctly. Nothing material is missing for an 8-param settings toggle.

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 the baseline is 3. The description does group the flags into recognizable categories (join notifications, boosts, setup tips, role-subscription purchases), which adds some framing, but it omits `role_subscription_replies` and `reason` entirely and adds no format or interaction details 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 and resource ("Toggle which automatic notices the system channel posts") and enumerates exactly which notices are covered, so an agent can map it to the intent without opening the schema. No sibling tool touches system-channel notices, and the flag list makes the scope 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?

"Only provided flags change" and "Requires Manage Server" give useful call context, but there is no when-to-use guidance relative to alternatives — e.g. reading current values via discord_get_guild_settings or neighbouring guild-setting tools is never mentioned. Usage is implied rather than directed.

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