list_courses

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

The description adds context about parameter behaviors (include, state, enrollment_state) beyond the annotations (readOnlyHint, openWorldHint). It does not contradict annotations and provides useful filtering details.

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 clear sentences with no unnecessary words. The first sentence states the purpose, and the second explains key parameters, making it highly readable and efficient.

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?

Given no output schema, the description explains the tool's purpose and parameters adequately. It does not mention pagination or return format, but for a list tool with annotations and sibling context, it is sufficiently complete.

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?

With 100% schema coverage, baseline is 3. The description adds meaning by explaining that 'include' adds optional fields with examples, 'state[]' filters by workflow state, and 'enrollment_state' filters by caller's enrollment state, enhancing understanding beyond the schema.

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 'List courses for the authenticated user,' specifying the verb and resource. It distinguishes from sibling tools like list_account_courses by focusing on the authenticated user's courses.

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 explains when to use the tool and the purpose of each parameter but does not explicitly mention when not to use it or provide alternative tools. It is clear for a basic listing tool.

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