lms_list_courses

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

With no annotations, the description carries the behavioral burden. It clearly signals a non-mutating retrieval ('Return') and identifies the external SPADA portal as the source, but it does not disclose authentication requirements, failure behavior, or pagination. This is acceptable for a simple read-only list operation, yet some behavioral gaps remain.

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?

A single sentence that front-loads the action and resource, and adds only the scoping context needed: current semester and source portal. Every phrase earns its place; there is 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?

At low complexity, with no parameters and an output schema available, the description covers what an agent needs to invoke the tool. It could have added a note on result format or authentication, but the output schema fills the main return-shape gap. It is complete enough though not exhaustive.

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?

There are zero parameters and the input schema covers 100% of them, so the baseline is 4. The phrase 'all enrolled' reinforces that the tool takes no filtering parameters, which is consistent with the empty 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?

Description opens with the action verb and exact resource, 'all enrolled academic courses,' then scopes to current semester and the SPADA portal source. This clearly distinguishes it from sibling tools like lms_list_assignments and lms_list_materials.

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 use whenever the agent needs a list of enrolled courses for the current semester, but it gives no explicit guidance on when to prefer alternatives or what to use for assignments, materials, or deadlines. There are no exclusions or condition-based routing, so guidance is adequate but not strong.

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