discord_get_forum_post

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

Discloses read-only behavior (matching annotation readOnlyHint=true), returns JSON object with specific fields, and mentions chronological order of messages. No contradictions with 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 covering purpose and usage with no redundancy. Could be slightly more concise but no wasted words.

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?

With 2 simple parameters and an output schema (not shown), description covers key aspects: what is returned, read-only nature, and how to call. Lacks mention of return format but output schema covers that.

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 coverage is 100%, so description adds minimal value beyond schema. Repeats that thread_id is needed and limit controls message count, with default and range already in 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 verb 'Get' and resource 'forum post's details' plus specifies included information (title, state, tags, message count, recent messages). Distinguishes from sibling tools like discord_get_forum_channels and discord_get_forum_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?

Explicitly says 'Read-only. Pass the post's thread_id.', guiding correct usage. However, does not explicitly state when to use this tool versus alternatives like discord_get_forum_threads for listing threads.

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