unregister_course

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

With no annotations, the description fully carries the burden. It declares the operation as a write that affects UTOL data, warns caution, explains the preview mode (no confirm), and notes execution is recorded in audit log. This discloses all key behavioral traits.

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?

Two concise sentences that front-load the purpose and then deliver critical behavioral details. Every sentence adds value with no redundancy or fluff.

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 tool with two parameters and no output schema, the description covers purpose, preview mode, audit logging, and caution. Could mention the inverse relationship with register_course, but overall it's complete enough for safe use.

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%, meeting the baseline. The description restates the confirm parameter's behavior from the schema but adds no new meaning beyond that. Since no extra parameter insight is provided, a score of 3 is appropriate.

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?

Description clearly states the action: unregister from a course (コースの受講登録を解除する). It distinguishes from the sibling register_course by being its inverse. The verb '解除する' specifies the operation on the resource 'コースの受講登録'.

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?

Provides clear context: it's a write operation affecting course registration, requires caution, and has a preview mode via confirm parameter. Explicitly describes when preview occurs (no confirm:true). Lacks explicit comparison to sibling tools, but the preview hint guides safe usage.

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