list_courses

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

Annotations include readOnlyHint=true, so the description doesn't need to repeat that. The description adds minimal behavioral context (authenticated user scope) but doesn't disclose details like pagination, ordering, or what 'current active' means. No contradiction found, and the annotation covers safety.

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, clear sentence with no filler. It is front-loaded and efficient, conveying the essential purpose without unnecessary detail.

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 simple list tool with good annotations and full param schema coverage, the description is adequate. However, it doesn't mention return format or any implicit behaviors like default scope (active enrollments), which the parameters imply. Given the sibling tools, a bit more context about scope filtering could be helpful.

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 100%, both parameters have descriptions in the schema. The tool description doesn't add extra meaning beyond what the schema provides, so the baseline 3 applies. It could have explained how the flags interact (e.g., include_all vs include_concluded).

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 clearly states the tool lists courses for the authenticated user, which is a specific verb+resource combination. It distinguishes from siblings by focusing on the user's own course list, though it could more explicitly differentiate from 'get_my_enrollments' or other listing tools.

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 usage for retrieving courses the user is enrolled in, but doesn't explicitly state when to use this versus alternative tools like get_my_enrollments or list_assignments. No exclusions or references to alternatives are provided.

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