Edit Discord Server

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

Annotations already indicate idempotent, write, and non-destructive behavior. The description adds that it returns updated server details but lacks information about required permissions, partial update behavior, or effects on unmentioned settings.

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 initial sentence is concise, but the arg list duplicates the input schema, making it longer than necessary. Could be more efficient by directing users to the schema for parameter details.

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?

For a tool with 8 parameters, a nested object, and no output schema, the description covers basic purpose and return type but lacks details on validation, partial updates, and response structure. Adequate but not comprehensive.

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 the schema fully describes each parameter. The description repeats parameter names and types but does not add meaningful semantic details beyond what the schema provides.

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?

Clearly states 'Edit server settings' with verb and resource, and lists example fields (name, verification level, system channel). Distinguishes from sibling tools like discord_edit_channel and discord_edit_role, which edit different resources.

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 implies usage for editing guild settings but does not explicitly state when to use this tool versus alternatives or provide exclusions. Context from sibling names helps, but no direct guidance is given.

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