create_course

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

No annotations are provided, so the description carries the full burden. It mentions auto-generated slug and conditional requirements (e.g., course_price required if paid_course). However, it does not cover other behavioral aspects like uniqueness of title, idempotency, or error handling.

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 front-loaded with the purpose, then lists all 18 parameters in a structured Args block. While comprehensive, it is somewhat verbose for the number of parameters; every sentence is earned but could be more concise.

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 the tool's complexity (18 parameters, no annotations) and the existence of an output schema, the description covers parameter semantics thoroughly and mentions auto-generated slug and conditional requirements. It does not explain return values, but that is covered by the output schema.

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 0%, so the description adds significant value by explaining each parameter's meaning, including conditional requirements. For example, 'short_introduction: One-line summary shown on course cards' and 'paid_course: Whether this is a paid course' provide context 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 'Create a new LMS Course', which specifies the verb and resource. It also adds that a URL slug is auto-generated. However, it does not distinguish itself from siblings like 'create_full_course', which might create a more comprehensive 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?

No guidance is provided on when to use this tool versus alternatives such as 'create_full_course' or 'reupload_course'. There is no context about prerequisites or situations where this tool is preferred.

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