create_course

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

With no annotations, the description carries the burden. It discloses the MOODLE_WS_COURSE_EXISTS error for duplicate idnumbers and states default visibility, format, and section count. Most defaults already appear in the schema, and it omits other behavioral details like permissions or side effects.

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?

Three concise sentences, front-loaded with the primary purpose, then error behavior and defaults. There is no filler; every sentence earns its place.

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 9-parameter creation tool with no output schema and no annotations, the description is too thin. It omits return value, permission requirements, and guidance for required fields, making it insufficient for an agent to invoke confidently without further schema inspection.

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 description coverage is only 22% (lang and idnumber_slug have descriptions). The description adds little beyond the schema: it mentions 'stable idnumber' and defaults but does not explain fullname, shortname, categoryid, summary, or numsections semantics, leaving a significant gap.

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 opens with 'Create a new Moodle course', using a specific verb and resource, and adds 'with a stable idnumber' to define scope. This clearly distinguishes it from sibling tools like update_course and duplicate_course.

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 phrase 'Create a new' clearly signals use for new course creation, and the idnumber uniqueness error implies create-vs-update context. However, it does not explicitly name alternatives like update_course or state when not to use the tool, so it misses a 5.

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