moodle_courses_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds the key scope that only 'enrolled' courses are returned, which is a useful behavioral constraint, but it doesn't elaborate on other behaviors like pagination, ordering, or error handling. Given the output schema exists, some structure is already covered.

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 concise sentence that directly states the action, resource, and output fields, with no wasted words or redundancy. It is efficiently structured and front-loaded.

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?

Although the tool is simple and has an output schema, the description omits any explanation of the 'site' parameter, provides no usage context, and doesn't indicate how this tool fits with its siblings. This leaves a significant completeness gap for an agent trying to invoke it correctly.

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 only parameter 'site' has zero schema coverage (no description in the schema) and the description does not mention it at all. This leaves the parameter's purpose completely unclear, and the description fails to compensate for the lack of schema documentation.

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') with a clear resource ('enrolled Moodle courses') and even specifies the return fields (id, shortname, fullname), making the tool's purpose immediately understandable. This clearly differentiates it from sibling tools like moodle_course_tree or moodle_course_download, which have different actions or scopes.

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 alternatives, nor any mention of prerequisites or context. It simply states the action without any usage direction, leaving the agent to infer when to choose this over sibling tools.

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