List Group Discussions

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

Annotations already establish readOnly and openWorld, but the description adds real behavioral substance: pagination at 100 per request, full-page fetching, and a hard failure with 'Results are incomplete' rather than silent truncation. It also warns replies are excluded, which prevents a wrong inference about the payload.

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?

Front-loaded with the resource and return shape, then the pagination caveat, then sibling routing; every clause is informative. It is a dense three-sentence block; the trailing note about missing counterparts for post_discussion_entry and list_announcements is the least essential piece.

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 no output schema, the description compensates by enumerating the returned fields and explicitly excluding replies, plus documenting pagination and failure behavior. Nothing an agent needs to invoke it correctly or interpret results is missing.

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?

There is a single parameter with 100% schema description coverage ('The Canvas group ID'), so the schema already carries the meaning. The description adds no further detail on group_id format or how to obtain it, making this baseline-level rather than value-adding.

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?

States a specific verb and resource with scope: 'List discussion topics in a group', and immediately enumerates the fields returned. It is clearly differentiated from its two nearest siblings (get_group_discussion, list_discussions), which are named explicitly.

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?

Gives explicit routing: use get_group_discussion for a single topic with due/available dates, list_discussions for the course-scoped equivalent. It also states a boundary ('there is no group-scoped counterpart to post_discussion_entry or list_announcements'), so the agent knows not to hunt for siblings that don't exist.

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