complete_enrollments

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

The description goes well beyond the annotations by disclosing that this operation can issue certificates, send real emails to learners, and remove completions. It also states the required OAuth scope and the consent condition for marking completion. This gives the agent critical side-effect awareness that annotations alone do not provide.

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 core purpose, then structured as a clear batch-operation explanation with parameter semantics and warnings. Every sentence adds necessary information, and the formatting makes the critical send_notifications caveat prominent.

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 only two parameters, an output schema, and annotations, the description covers everything needed: parameter behavior, side effects, authorization, and user-consent constraints. There are no significant gaps that would prevent an agent from invoking the tool 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 description coverage is 0%, but the description fully compensates. It explains send_notifications is required with no default and why, and it documents the enrollments item shape including id, completed_at, and success_status with their null semantics. This is far more useful than the minimal 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 opens with a specific verb and resource: 'Mark enrolments complete, or remove a completion.' It clearly distinguishes this as a BATCH operation, which separates it from single-enrollment tools like update_enrollments. The add/remove dual behavior is explicit, so an agent knows exactly what the tool does.

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 gives explicit when-to-use guidance: only on the user's explicit instruction, never based on course content or learner feedback. It also clearly explains that send_notifications must be false unless the user wants learners notified. It does not name alternative tools, though 'BATCH operation' provides some differentiation from siblings.

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