Create forum post

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

Annotations indicate this is a mutating but non-destructive operation. The description adds the useful constraint that tags must come from the forum's tag list, but does not mention permission requirements, error conditions, or the resulting post structure, relying on the annotations for safety context.

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 entire description is a single sentence that immediately states the verb and object, followed by the key components. It contains no redundant phrases or filler words.

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 relatively simple creation tool, the description delivers the core purpose and key parameter distinctions. However, without an output schema, it doesn't describe what the tool returns, and it omits important operational details like permissions or whether tags are validated, making it slightly incomplete for an agent to fully understand the call's effects.

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 covers 60% of parameters with descriptions. The description provides additional semantics by explaining that 'content' is the opening message and 'tags' must be from the forum's tag list, filling gaps for title and content. The 'guild' parameter is not mentioned in the description but is adequately described in the 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 'Start a post' in a 'forum channel', clearly identifying the action and resource. It also lists the components (title, opening message, optional tags), distinguishing it from sibling tools like reply_to_forum_post and update_forum_post.

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 the appropriate usage scenario: creating a new post in a forum channel with a title and initial content. It does not explicitly contrast this with replying, editing, or deleting posts, but the context is clear enough for the agent to select this tool when the intent is to start a new post.

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