discord_update_forum_post

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

Adds context beyond annotations: explains that archiving is safe (not a delete), that passed tags replace existing tags, and notes permission requirement. No contradiction with annotations (readOnlyHint=false, idempotentHint=true).

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 sentences, each earning its place: what it updates, how partial updates/tag replacement work, and permission requirement. No redundancy or fluff.

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?

Covers input behavior thoroughly for a mutation tool with no output schema and 5 parameters. Missing return value specification (e.g., returns updated post?) but acceptable given typical Discord tool conventions.

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 covers all 5 parameters individually (100% coverage). Description adds behavioral nuance: partial updates, tag replacement behavior. Provides some additional meaning but schema already does heavy lifting.

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?

Clearly states verb 'update' and resource 'forum post', listing specific fields (title, archived/locked state, applied tags). Distinguishes from siblings like delete and create by focusing on partial updates.

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?

Provides prerequisite (Manage Threads permission) and clarifies archiving as non-destructive closure. Implies partial update behavior but does not explicitly exclude alternatives like discord_set_forum_tags for tag-only updates.

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