Create forum post

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

Annotations already indicate a non-destructive write operation. The description adds that it creates a forum post, which is consistent. No further behavioral traits (e.g., required permissions, side effects like thread creation) are disclosed, but it doesn't contradict 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?

The description is a single, clear sentence that front-loads the action and efficiently covers the key components. There is no wasted text.

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?

The description lacks important context such as the fact that forum posts are threads, what the return value is (e.g., the created post object), or any required permissions. Given the tool's complexity and lack of output schema, more detail is needed for the agent to invoke it correctly.

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 60%; the description adds context by labeling 'content' as 'opening message' and noting tags are optional. This provides some extra meaning beyond the schema, but does not fully compensate for the missing schema descriptions on 'title' and 'content'.

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 clearly states the verb 'Start a post' and resource 'forum channel', and lists the components (title, opening message, tags). It does not explicitly differentiate from sibling tools like 'reply_to_forum_post' or 'create_thread', but the purpose is 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?

Usage is implied by the description: 'Start a post' suggests creating a new discussion in a forum. However, there is no explicit guidance on when to use this tool versus alternatives like 'reply_to_forum_post' or 'create_thread', leaving the agent to infer from context.

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