create_course

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

The description discloses non-idempotency ('a repeated call can duplicate the effect'), live-world mutation, server-side auth injection, throttling, and error/status behavior. This goes well beyond what the annotations alone provide and remains consistent with readOnlyHint=false and idempotentHint=false.

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 longer than average but well-structured into labeled sections (Behavior, Parameters, Returns, Use when) and front-loads the key information. Minor redundancy exists, such as both 'creates data' and 'Creates a new course' earlier in the text, but it remains efficient and scannable.

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 mutation tool with no output schema, the description covers creation semantics, non-idempotence, authentication, rate limiting, error handling, parameter forwarding, and when to use it. Nothing critical is missing for an agent 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?

Schema coverage is 100%, including descriptions for nested fields, so the schema already documents the body contents. The description adds valuable semantics: the entire payload goes in the single 'body' argument, is forwarded verbatim, and although the spec marks body optional, this endpoint expects one.

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 states a specific verb and resource: 'Creates a new course' via POST /v2/courses, and identifies the response as the created Course resource. This clearly distinguishes it from sibling tools like get_course, update_course, and create_course_section.

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?

Explicitly says 'Use when: only when the user asked to create this,' and instructs to check with a read tool that the target exists and the record is not already there. It also names related Courses tools, giving the agent concrete guidance on alternatives.

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