classroom_list_courses

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds valuable behavior: only one page is returned as {items, nextPageToken}, and callers must continue until nextPageToken is null. However, it omits that courseStates also permits DECLINED and SUSPENDED, which slightly reduces 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?

Two sentences with no filler: purpose, filter support, and pagination behavior are each stated once. The most important information is front-loaded and every sentence earns its keep.

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 covers core list/pagination behavior and state filtering, and the readOnly annotation covers the safety profile. But with no output schema and low schema description coverage, the lack of any explanation for fullData and pageSize, plus the incomplete state list, leaves noticeable gaps.

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 only 25%, but the description partially compensates by explaining courseStates values and the pageToken-based continuation. pageSize is reasonably inferable from its name and limits, but fullData is entirely unexplained in both schema and description, leaving a real gap.

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 uses a specific verb ('List') and resource ('Google Classroom courses'), with a clear scope ('all') and state-filtering behavior. It is clear but does not explicitly distinguish itself from the sibling classroom_search_courses, so it misses the top score.

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 clear context for when to use the tool: to list all courses or filter by state, and to paginate by following nextPageToken until null. It does not name sibling alternatives such as classroom_search_courses or state when not to use this tool, so it falls short of explicit exclusions.

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