jcourse_delete_enrollment

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds a behavioral gate that the annotations do not: confirm=true is required, tying execution to explicit user authorization. It stops short of saying the deletion is irreversible or what the response reports.

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 short clauses separated by a semicolon, with the action front-loaded and the two operational requirements packed into the tail. There is no redundant restatement of the tool name or annotations.

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?

An output schema exists, so return values need not be described, and annotations cover the destructive/non-idempotent profile. The only remaining gap for a destructive mutation is the absence of any note on irreversibility or on what happens when the enrollment no longer exists.

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%, so the baseline is 3, but the description adds provenance for enrollment_id (it comes from jcourse_list_enrolled_courses), which the schema only describes as 'a platform object ID, positive integer'. It also reinforces the confirm=true requirement consistent with the schema's default of false.

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?

States a specific verb plus resource ('删除一条我的选课记录'), and the qualifier '我的' scopes it to the caller's own enrollments, distinguishing it from sibling deletion tools like jcourse_delete_review. An agent can identify exactly what object is affected without opening the schema.

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?

Names the workflow prerequisite explicitly: the enrollment_id must come from jcourse_list_enrolled_courses, and confirm=true must be set. It gives the correct upstream tool for obtaining the ID but does not state when deletion should be avoided or what to do if the enrollment is already gone.

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