discord_update_forum_post

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

Description adds important behavior beyond annotations: 'applied_tags replaces the post's tags' and 'archived:true to close without deleting'. Permissions context also disclosed. Annotations already indicate non-destructive, idempotent, open-world; description aligns and supplements.

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 tightly written sentences, no wasted words. Front-loaded with primary purpose, then key behaviors, then prerequisite. Every sentence adds value.

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 main behavior, parameter effects, and permission requirements. Lacks return value description but acceptable given no output schema. Complete enough for a mutation tool with idempotent hint.

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 params with descriptions (100% coverage). Description adds semantic nuance: 'Only provided fields change' and explains applied_tags replacement behavior, which goes beyond 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?

Description clearly states the tool updates a forum post's title, archived/locked state, or applied tags. It distinguishes from create/delete siblings by focusing on modification.

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?

Explicitly notes that only provided fields change, and gives specific guidance for archiving vs. deleting. Mentions permission requirement. Could be improved by noting when to use alternative tools like set_forum_tags.

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