discord_create_forum_post

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

Annotations already establish this as a write, non-idempotent, non-destructive operation. The description adds value beyond that by disclosing required permissions, the return payload (post name and thread ID), and the thread-plus-starter-message structure. It does not contradict any annotation, but failure behavior is not addressed, preventing a 5.

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?

Four short sentences, each carrying distinct value: purpose, prerequisites, alternative routing, and return value. The core action is front-loaded and there is zero filler or repetition of schema content.

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?

Since no output schema exists, the description correctly takes responsibility for disclosing the return value (post name and thread ID), and it covers prerequisites and the most relevant sibling. Remaining gaps are minor — failure modes and invalid tag handling are not mentioned — but for a 4-parameter write tool this is largely 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?

Schema description coverage is 100%, so the baseline of 3 applies. The description adds no parameter-level detail beyond what the schema already documents — for example, title-as-thread-name and content-as-starter-message are both already stated in the schema property descriptions.

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 opens with a specific verb+resource: 'Create a new post (a thread with a starter message) in a forum channel.' The parenthetical clarifies that a forum post is a thread plus a starter message, distinguishing this tool from discord_send_message and discord_create_thread without needing to inspect either schema.

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 names the sibling alternative and the condition that selects it: 'Use discord_reply_to_forum to add follow-up messages,' which tells the agent when NOT to use this tool. It also states the prerequisite permissions (Send Messages and Create Public Threads) that gate invocation.

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