getClientEnrollments

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

With no annotations, the description carries the full burden of disclosure, but it only states 'Get client's enrollments' without clarifying whether the enrollments are active, historical, sorted, or how the response is structured. This minimal wording does not add meaningful behavioral context beyond the tool's name.

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 a single, short phrase with no wasted words, making it easy to parse. However, it is so terse that it verges on under-specification, though it remains appropriately concise for a simple getter.

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 the simplicity of the tool (one parameter, no output schema), the description is minimally adequate but leaves questions unanswered, such as whether enrollments are filtered by status or date. The existence of getEnrollments as a sibling also adds ambiguity that the description does not address.

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 input schema fully covers the only parameter (clientId) with 'Client ID', and the description adds no additional meaning about the parameter's format or usage. With 100% schema coverage, this meets the baseline for parameter documentation.

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 identifies the action ('Get') and the resource ('client's enrollments'), making the tool's function understandable. However, it does not explicitly differentiate this from the sibling tool getEnrollments, which could cause confusion about the scope.

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 no guidance on when to use this tool versus alternatives like getEnrollments or getClientMemberships. It also fails to mention prerequisites, such as the need for a valid clientId.

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