canvas_list_discussion_topics

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

The description repeats the 'read-only' annotation without adding additional behavioral context. It does not mention pagination, default ordering, or the behavior of the 'onlyAnnouncements' filter, which would be valuable beyond the annotation.

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 a single sentence, which is concise, but it contains redundant information ('read-only') that is already in the annotations, and it omits useful parameter details. It is not overly verbose, but it is under-specified.

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 list tool with three parameters and no output schema, this description is incomplete. It leaves the agent without information about the enum values for orderBy, the semantics of onlyAnnouncements, or the structure of the response, making it hard to select and invoke the tool correctly in varied contexts.

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 0% description coverage, and the tool description does not explain any of the three parameters (courseId, orderBy, onlyAnnouncements). For example, it does not clarify that orderBy accepts position, recent_activity, or title, or what onlyAnnouncements does.

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 uses a specific verb ('List') and resource ('discussion topics for a course'), making the tool's function clear. However, it does not explicitly distinguish from the sibling tool 'canvas_list_announcements', which may overlap in functionality.

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 no guidance on when to use this tool versus its siblings, such as 'canvas_list_announcements'. There is no mention of filtering by announcements or ordering, nor any exclusions.

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