discord_create_forum_post

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It states it 'creates' (implying a write/mutation) and mentions optional tags, but doesn't disclose permissions required, rate limits, error conditions, or what happens on success (e.g., returns post ID). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence with zero waste. It's front-loaded with the core action and resource, and the optional feature is succinctly added. Every word earns its place, making it easy to parse quickly.

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?

Given the tool's complexity (a mutation with 4 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions or errors, parameter details, or return values. For a Discord API tool that likely has specific constraints, this leaves the agent under-informed.

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 0%, so the description must compensate but adds little. It mentions 'optional tags' which maps to one parameter, but doesn't explain forumChannelId (what format, how to obtain), title (character limits), content (formatting), or tags (allowed values). With 4 parameters and low coverage, the description fails to provide meaningful semantics beyond 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 clearly states the action ('Creates a new post') and resource ('in a Discord forum channel'), with an additional feature ('with optional tags'). It distinguishes from siblings like discord_send (general message) or discord_reply_to_forum (reply to existing post), though not explicitly named. However, it doesn't specify what makes a forum post unique versus other channel types, slightly limiting differentiation.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing forumChannelId from discord_get_forum_channels), exclusions (e.g., not for text channels), or compare to siblings like discord_send or discord_reply_to_forum. Usage is implied only by the tool name and basic action.

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