moodle_list_courses

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context by explaining the classification values (inprogress means current semester), but it does not disclose return format, pagination, or other behavioral details. This is adequate but not rich.

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 with a parenthetical for the parameter values. It is front-loaded with the main action and resource, and every word earns its place with no redundancy.

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 one optional parameter and no output schema, the description is largely complete. It specifies the resource and the filtering options. It could be slightly more explicit about what '选修的课程' includes (e.g., only enrolled courses), but overall it adequately covers the tool's behavior.

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 has one parameter with enum values but no descriptions. The description explicitly explains each enum value (inprogress, past, future, all), adding meaning beyond the schema and compensating for the 0% schema description coverage. This is clear and helpful for a single parameter.

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 action ('list') and resource ('elective courses'), and the classification parameter further specifies the scope (inprogress/past/future/all). It distinguishes itself from other Moodle list tools by focusing specifically on courses rather than forums, assignments, etc.

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?

No guidance is provided on when to use this tool versus alternatives like moodle_get_course_contents or ed_list_courses. The usage is only implied through the action 'list', but no explicit context or exclusion criteria are mentioned.

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