get_enrollment

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

Annotations already mark this as read-only and idempotent, and the description adds useful behavioral context: it requires the 'enrollments:read' OAuth scope and states exactly which fields will be returned. This goes beyond the annotations without contradicting them.

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 compact and front-loaded: purpose first, then return fields, then parameters and auth. No filler or repetition of schema details.

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 read-only lookup with one required parameter, the description is complete: it explains what it fetches, what it returns, what 'include' accepts, and the required OAuth scope. The output schema and annotations cover the remaining structured details.

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 0%, so the description carries the parameter burden. It clarifies that 'id' is the Skilljar enrollment id and lists accepted values for 'include' (purchase, student, certificate), adding real meaning beyond the bare schema. It doesn't specify whether multiple include values are supported or how they behave, but it is still helpful.

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: 'Fetch one enrolment by its Skilljar id.' It clearly distinguishes itself as a single-record lookup with a course-level reporting focus, and enumerates the exact return fields, separating it from list-style or progress-oriented siblings.

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 implies when to use it: when you need a single enrollment's score and progress rather than a list. It says 'one learner on one course', which frames the use case, but it does not explicitly name alternatives like list_enrollments or get_learner_progress.

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