List Course Roster

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds useful behavioral context by specifying the return fields and the caveat that email visibility depends on scope and domain permissions.

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 well-structured: a one-sentence purpose, an Args list, and a Returns line. There is no fluff, though the Args block partially duplicates the schema.

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 no output schema, the Returns line is valuable and explains what the agent will receive. It covers role, limit, response format, and email visibility caveats. It omits pagination or error behavior, but for this simple read-only roster tool, the description is adequately complete.

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 Args section largely restates what the input schema already provides. It does add a human-readable constraint for limit ('Max 1-200 (default 100)'), which the schema only expressed via min/max/default values, but it does not deeply enrich course_id or response_format beyond the schema descriptions.

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 'List students or teachers enrolled in a course,' which is a specific verb and resource. This clearly distinguishes it from sibling list tools such as classroom_list_courses, classroom_list_coursework, and classroom_list_announcements.

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 provides clear context for when to use this tool: fetching roster members for a course. It does not explicitly name alternatives or state when not to use it, but the purpose is unambiguous enough that an agent can route correctly.

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