discord_update_forum_post

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

There are no annotations, and the description does not disclose behavioral details such as whether tag replacement is idempotent, how locking/archiving interacts, or any side effects on the post. The schema notes that tags replace all existing tags, but the main description itself lacks such 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, concise sentence that starts with the action verb 'Updates' and immediately lists the relevant fields. There is no redundant wording or extraneous information.

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 combined with the fully documented schema provides enough context for a straightforward update operation. It lacks only guidance on expected outcomes or errors, but these are not critical for invoking the tool with the provided parameters.

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 parameter descriptions cover 100% of the parameters, so the baseline is 3. The main description adds no additional semantic detail beyond what the schema already provides; for example, 'Tags can be specified by name or ID' is already present in the schema description.

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 tool updates a forum post's title, tags, archived status, locked status, or pinned status. The verb 'Updates' and the specific resource and properties make the purpose unambiguous, and it differentiates from siblings like discord_set_forum_tags which only handles tags.

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 does not provide explicit guidance on when to use this tool versus alternatives such as discord_set_forum_tags or discord_delete_forum_post. There is no mention of conditions or scenarios that would favor this tool over siblings, leaving the user to infer usage from the property list.

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