getEnrollments

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

No annotations are present, so the description carries the full burden of behavioral disclosure. 'Get enrollments' implies a read operation but does not mention filtering behavior, return format, pagination, authentication, or any side effects. The parenthetical adds domain context but not behavioral transparency.

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, efficiently worded sentence with the verb and resource front-loaded. The parenthetical elaboration is purposeful, avoiding redundancy. There is no wasted text, making it appropriately concise for a simple getter tool.

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?

With 9 optional parameters, no annotations, and no output schema, the description is too sparse. It does not explain the response structure, the meaning of the filter parameters, or any constraints. This is insufficient for an agent to use the tool correctly without additional inference.

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 100%, so the baseline is 3. The description adds no parameter semantics beyond the schema, but the schema's parameter descriptions are minimal (e.g., 'Start date', 'Staff IDs') and do not explain how filters combine or interact. No additional value is provided, so the baseline stands.

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 a specific verb and resource: 'Get enrollments' with a parenthetical scope ('courses, workshops, series'). This provides enough clarity to distinguish from generic list tools, though it does not explicitly differentiate from the sibling getClientEnrollments or explain the distinction between client-specific and overall enrollments.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools like getClientEnrollments, getClasses, and getScheduleItems, the description offers no usage context, exclusions, or prerequisites, leaving the agent to guess the appropriate selection criteria.

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