List course messages

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only safety profile is established. The description adds value by disclosing the dual behavior (list threads vs. read messages in a thread), but it does not address ordering, pagination, or what occurs when conversationId is combined with limit. It adds context without contradiction, earning a mid score.

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?

A single, tightly written sentence that front-loads the primary behavior and appends the optional mode. No wasted words, though it could marginally benefit from a usage hint. Efficient and well-structured.

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 listing tool with moderate complexity (3 parameters, no output schema), the description conveys the essential behavior and the two invocation modes. Without an output schema, it does not specify return format, but the dual-mode clarity is sufficient for an agent to call it correctly. Minor gaps around limit/pagination remain.

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 67%, with courseId and conversationId already documented in the schema. The description implicitly maps 'message threads' to the default and 'messages inside one thread' to conversationId, but adds no new detail about limit semantics or value formats. At this coverage level, the baseline of 3 is appropriate.

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 states a specific verb (lists) and a precise resource type (message threads / 'conversations' in a course), and additionally discloses the dual-mode behavior of optionally listing messages inside a thread. This clearly differentiates it from siblings like bb_list_discussions, which covers discussion forums rather than course messages.

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 gives no explicit when-to-use or when-not-to-use guidance, and does not name any alternative tool. With several plausible siblings (bb_list_discussions, bb_announcements, bb_todo) that an agent could confuse for message-like content, the lack of routing guidance is a notable gap.

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