list_courses

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

With no annotations, the description carries the burden of behavior disclosure. It mentions access scope ('courses you have access to'), the return value (IDs), default filtering ('active courses by default'), and admin-only search behavior. This adds context beyond the schema, though it omits details like pagination or outcome shape beyond IDs.

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 focused sentences that succinctly cover purpose, core output, default behavior, and admin capability. Every clause adds value with no filler.

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?

As a simple list tool with two optional parameters and no output schema, the description adequately covers the main use case and the critical return value (course IDs). It could benefit from mentioning pagination or additional fields returned, but these are not essential for basic use.

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 descriptions already cover both parameters (search_term: admin-only, enrollment_state: filter with default active). The description repeats these concepts without adding new semantic detail. Since schema coverage is 100%, 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 opens with 'List Canvas courses you have access to,' which is a specific verb+resource statement. It further clarifies its role by noting it 'Returns course IDs needed by all other tools,' distinguishing it from more specialized sibling tools like list_sections or list_terms.

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 implies a primary use case: fetch course IDs before using other tools. It also provides conditional guidance for admins wanting to search all courses. However, it does not explicitly name alternatives or state when not to use this tool.

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