discord_create_forum_post

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

Annotations already indicate mutable, non-destructive, non-idempotent behavior. Description adds permission requirements and return value (name and thread ID) but omits rate limits, error conditions, or side effects beyond creation.

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?

Two sentences plus a permission note, front-loaded with the core action, no fluff. Every sentence earns its place.

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?

No output schema, so description correctly states return value. Covers creation, required permissions, and sibling tool for next action. Missing error handling or tag validation details but sufficient for a 4-param tool.

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 covers 100% of parameters with descriptions, so baseline is 3. The tool description adds no extra parameter meaning beyond what schema already provides (e.g., max lengths are in 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?

The description uses the specific verb 'Create' with the resource 'forum post', clarifies it as 'a thread with a starter message', and differentiates from sibling 'discord_reply_to_forum' for follow-up messages, making the purpose 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?

Explicitly states required permissions (Send Messages, Create Public Threads) and directs to use 'discord_reply_to_forum' for follow-ups. Lacks explicit 'when not to use' but clear enough.

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