Remove Enrollment

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

The description adds transparency beyond the destructiveHint annotation by explicitly stating that 'delete' is permanent while 'conclude' and 'deactivate' are reversible. This discloses the key behavioral difference between the operations. It does not contradict annotations, and it provides useful context about the consequences of each task.

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 concise and well-structured, with two clear sentences. It avoids unnecessary detail and gets straight to the point, providing essential information without 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?

Given that this is a destructive operation, the description adequately covers the permanence aspect. It does not mention side effects or prerequisites, but for a simple removal tool, it provides enough context. The absence of an output schema makes it acceptable that no return values are described.

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?

The schema already describes each parameter, and the description adds value by elaborating on the 'task' parameter, explaining that delete is permanent and others are reversible. This clarifies the meaning of the enum values. For course_id and enrollment_id, the schema descriptions suffice, so the additional context is minimal but beneficial.

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 the tool's purpose: removing or concluding an enrollment from a course. It specifies the action (remove/conclude) and the resource (enrollment) in context, and distinguishes between delete (permanent) and conclude/deactivate (reversible), making it distinct from other tools.

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 description provides implicit usage guidance by differentiating the three task types (delete vs. conclude vs. deactivate) and their reversibility. While it does not explicitly mention alternatives, it is the only enrollment removal tool among siblings, making its purpose clear enough. The note about permanence helps users choose the appropriate task.

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