discord_get_forum_post

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

Annotations already indicate readOnlyHint=true. The description adds value by stating messages are returned 'oldest-to-newest' and listing the specific fields (title, archived/locked, tags, message count). This provides behavioral context beyond 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?

Two sentences: first sentence lists all returned fields, second sentence confirms read-only nature, explains required parameter, and mentions return format. Every sentence is meaningful, no redundancy.

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?

For a tool with 2 parameters, no output schema, and clear annotations, the description adequately explains what is returned (including list of fields and ordering). It is complete enough for an agent to understand the tool's behavior and 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 description coverage is 100%, so baseline is 3. The description restates thread_id's purpose and provides default/range for limit, but does not add new semantic meaning beyond what the schema already specifies.

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 gets a forum post's details (title, archived/locked state, applied tags, message count) and recent messages. It explicitly says 'read-only' and specifies the output is a JSON object. This distinguishes it from sibling tools like create, delete, update, or reply operations.

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?

Description says to 'pass the post's thread_id', providing clear usage context. While it doesn't explicitly state when not to use this tool or compare with siblings like discord_read_messages or discord_get_forum_threads, the purpose is specific enough that an agent can infer its appropriate use.

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