list_forums

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

With no annotations, the description carries the full burden. It discloses that the tool lists forums and returns specific fields (id, name, type, description). It also explains the parameter behavior. It could explicitly note that it is a read-only operation, but the listing nature implies non-destructive behavior.

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 two sentences with no wasted words. The first sentence states the main purpose, and the second clarifies the parameter behavior. It is front-loaded and concise.

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 optional parameter, the description is complete: purpose, return fields, parameter behavior. No output schema needed. Could mention relationship to get_forum_discussions, but not essential.

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 has one parameter (course_ids) with no description, and schema coverage is 0%. The description compensates fully by explaining that omitting course_ids scans all courses, adding meaning beyond the 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?

The description clearly states the tool lists forums in courses, includes news/announcements, and distinguishes from sibling tools like get_forum_discussions. It specifies the verb 'list', the resource 'forums in your courses', and notes that it returns forum_id, name, type, and description.

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?

The description provides clear context: if course_ids is omitted, it scans all courses. This guides when to provide the parameter. However, it does not explicitly state when not to use this tool or mention alternatives, though the sibling get_forum_discussions is implied as a follow-up.

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