discord_get_forum_post

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

With no annotations, the description must carry full behavioral disclosure. It mentions the tool 'Retrieves details' but does not state whether it is read-only, whether it requires authentication, how it handles missing posts, or any pagination/rate-limit behavior. This leaves significant ambiguity.

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 sentence with no filler, but it is under-specified. It is concise but not well-structured for the agent's needs, lacking any breakdown of details, return type, or usage context.

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?

Given the lack of an output schema and annotations, the description should explain what is returned (e.g., message list, metadata, ordering) and any limitations. It does none of this, making the tool under-specified for a one-parameter getter.

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?

The schema defines one parameter 'threadId' (string) with no description. The tool description adds no explanation of what a threadId is, how to obtain it, or how it relates to a forum post. Since schema coverage is 0%, the description does even less to compensate.

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 specifies the action ('Retrieves details') and the resource ('forum post'), including that it also gets 'its messages'. This distinguishes it from list-type tools, but not from the sibling discord_get_forum_post_stream, which likely has a similar retrieval purpose.

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?

There is no guidance on when to use this tool versus alternatives like discord_get_forum_post_stream or discord_list_forum_threads. No context is provided about prerequisites, filtering, or scenarios where one tool would be preferred.

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