discord_modify_guild

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

No annotations are provided, so the description carries the full burden. It only says 'Modify guild-level settings' without disclosing side effects, permission requirements, reversibility, or the significance of the dryRun parameter (which defaults to true). This leaves behavioral expectations unclear.

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 a single, front-loaded sentence with no filler: 'Modify guild-level settings such as...' It is appropriately concise and easy to parse.

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?

Given the open-ended body schema and no output schema, the description is too sparse. It does not describe the structure of the body (e.g., partial vs. full update), the purpose of dryRun, or how to interpret the response. More context is needed for reliable invocation.

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?

The schema has 0% description coverage, so the description must compensate. It names several body properties (name, description, locale, verification, rules channel, safety channels), giving partial semantics for the body object, but it does not explain guildId, dryRun, or reason. Since the body is open-ended, these examples are helpful but incomplete.

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 clearly states the action ('Modify') and the resource ('guild-level settings'), and enumerates example fields (name, description, locale, verification, rules channel, safety channels). This distinguishes it from sibling tools like discord_get_guild (read), discord_upsert_channel (channels), and discord_upsert_role (roles).

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?

No guidance is given on when to use this tool versus alternatives. It does not mention that discord_get_guild should be used for reading, or that discord_raw_guild_request can be used for low-level requests, nor does it specify prerequisites like required permissions.

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