discord_reply_to_forum

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

Annotations already indicate a write operation (readOnlyHint=false), but the description adds useful context beyond that: the required 'Send Messages in Threads' permission and the fact that the tool 'Returns the new message ID'. This enriches the agent's understanding without contradicting the 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?

Three targeted sentences carry the action, permission requirement, alternative, and return value without redundancy. It opens with the core purpose and 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?

The tool is simple, both required parameters are fully documented in the schema, annotations cover the write nature, and the description provides the missing return information. An agent has everything needed to select and invoke this tool 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 coverage is 100%, and both parameters already have clear descriptions in the schema: content is a max-2000-character plain-text body, and thread_id is the snowflake ID of the forum post. The description adds no extra parameter-level meaning beyond the schema, so baseline 3 is appropriate.

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: 'Post a follow-up message inside an existing forum post (thread)', identifying both a specific verb and resource. It also distinguishes itself from discord_create_forum_post by explicitly saying that tool is for starting a new post instead.

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 gives explicit when-to-use context: 'inside an existing forum post'. It also names the alternative, discord_create_forum_post, and tells the agent to use that instead when starting a new post. The permission requirement further clarifies the conditions under which this tool can be used.

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