canvas_list_enrollments

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

The readOnlyHint annotation already signals a safe read operation. The description adds that only 'active' enrollments are included, which is useful behavioral context. However, it does not disclose return format, filtering details, or any other behavioral traits beyond what the annotation and field list imply.

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, focused sentence that is front-loaded with the action and resource. It avoids redundancy and includes specific grade fields without unnecessary elaboration.

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 tool is simple (one optional parameter, no output schema), and the description names the returned grade fields, which helps set expectations. However, it omits the meaning of observeeId and any default behavior when the parameter is absent, leaving a noticeable gap in completeness.

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 schema has no description for observeeId, and the tool description does not explain it either. With 0% schema description coverage, the description should compensate and clarify the meaning and behavior of the single parameter, but it fails to do so.

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 lists active student enrollments with per-course grades, naming specific fields. This distinguishes it from sibling tools like canvas_list_missing_submissions or canvas_list_assignments, which serve different purposes.

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. The optional observeeId parameter is ambiguous — it is unclear whether omitting it returns enrollments for all students or something else, and no context 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.