canvas_list_discussions

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

With no annotations, the description carries the full behavioral burden but only states the scope. It says nothing about pagination, result limits, ordering, or required permissions — notable gaps for a list operation. It does disclose the CANVAS_DEFAULT_COURSE_ID fallback, which is the one piece of added behavioral context.

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?

Very short and front-loaded, with the core purpose in the first sentence. The 'Args:' block is somewhat redundant with the schema but not wasteful.

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?

An output schema exists so return values needn't be explained, and the single parameter is covered. But as a list tool with no annotations, it omits pagination and result-set behavior, leaving meaningful gaps for correct invocation.

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 0% and the schema default is an empty string, so the description adds real value by explaining that course_id is numeric and falls back to CANVAS_DEFAULT_COURSE_ID. With a single parameter, this adequately compensates for the schema gap.

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 ('List discussion topics in a course'), which naturally distinguishes it from canvas_get_discussion and canvas_create_discussion. However, it does not explicitly name those siblings or clarify the boundary (e.g. list all vs. fetch one).

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?

No when-to-use guidance, prerequisites, or alternatives are given. The agent must infer that this is the bulk-retrieval counterpart to canvas_get_discussion from the verb alone.

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