get_courses_enrollments_user

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value beyond annotations by specifying pagination (limit of 50 per page) and the HTTP endpoint. No contradictions with annotations.

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 with three sentences plus a header. It front-loads the purpose and includes the endpoint. Minor fluff (emoji and 'Users') but overall efficient. Slightly redundant with the title in annotations.

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?

The description adequately explains that it returns a paginated list of course enrollments. However, without an output schema, it does not detail the structure of the enrollment data, which could be important for an agent. The lack of return format detail is a gap.

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 100%, so the description does not need to add parameter details. The description mentions pagination but does not add specific format or constraints beyond what the schema already provides for 'id' and 'page'. Baseline score of 3 is appropriate.

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 retrieves courses (enrollments) of a user with the verb 'Get' and resource 'courses/enrollments of user'. It distinguishes itself from sibling tools like 'get_course' and 'get_courses' by specifying user-specific enrollment data.

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 implicitly suggests use for retrieving user enrollments, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'get_products_user', 'get_user_progress'). No exclusions or prerequisites are mentioned.

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