list_forum_discussions

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

With no annotations, the description carries the burden. It explicitly discloses the return format (JSON array with subject, author, message, reply count, dates) and notes that message content is included. However, it does not mention any permissions, rate limits, or state that it is read-only, though 'List' implies a read operation.

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 compact and well-structured with a clear statement, an Args section, and a Returns section. Every sentence adds value; there is no redundant text 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?

For a simple list tool with one parameter and an output schema, the description provides sufficient context: it explains the parameter and describes the return payload. It does not mention pagination or potential size limits, but these are not critical for a basic listing operation.

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 only provides parameter name and type with 0% coverage. The description adds meaning by explaining what forum_id represents and directs users to list_forums to get it. This compensates well for the schema's lack of detail.

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 it lists discussions in a forum, including message content. The verb 'List' and resource 'discussions in a forum' are specific, and it distinguishes from sibling list_forums by targeting discussions within a forum rather than the forums themselves.

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 a useful prerequisite by referencing list_forums to obtain the forum_id, but does not explicitly explain when to use this tool over alternatives like create_forum_discussion or reply_forum_post. The usage context is implied but not formally contrasted with sibling tools.

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