discord_create_forum_channel

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

Discloses the permission requirement and return value (name and ID). Annotations already indicate non-read-only and non-destructive nature; the description adds context beyond annotations.

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 concise sentences with front-loaded purpose, no redundant or extra words. Every sentence serves a purpose.

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?

Covers all essential aspects: purpose, permission, sibling differentiation, return value. With 100% schema coverage and no output schema, the description is sufficiently complete.

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?

Input schema covers all 4 parameters with descriptions, so description adds minimal parameter-level detail. However, it notes the return value, which is helpful given no output 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?

Clearly states the tool creates a forum channel, distinguishes it from text/voice channels by mentioning 'forum holds posts (threads)' and explicitly referencing the sibling tool discord_create_channel.

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?

Explicitly tells when to use ('for forum channels') and when to use an alternative ('discord_create_channel for text/voice channels'), plus mentions required permission ('Manage Channels').

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