list_courses

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

With no annotations, the description carries the full burden. It usefully discloses that results are scoped to the signed-in account and cover both teacher and student roles, but it says nothing about pagination, result limits, ordering, or required OAuth scopes for a list operation that can grow large.

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 purpose sentence is front-loaded and the parameter note is compact and free of padding. Slightly more structure than needed for a one-parameter tool, but nothing wasteful.

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?

For a simple single-parameter read tool with no output schema and no annotations, this is close to sufficient, but a listing tool should mention pagination behavior or a result cap so the agent knows how to retrieve everything. That omission is the main remaining 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 description coverage is 0%, so the description must compensate and largely does: it explains course_states is optional, gives the full value set (ARCHIVED, PROVISIONED, DECLINED, SUSPENDED alongside ACTIVE), and notes that multiple values can be combined. The only gap is the stated default ["ACTIVE"] differing from the schema's null default.

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?

States a specific verb and resource ("List Google Classroom courses") plus the scope ("for the signed-in account") and the two role perspectives covered (teacher or student). This clearly distinguishes it from siblings like get_course or list_coursework, though it doesn't name those alternatives.

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?

Usage is implied by the verb and the account scoping, but there is no explicit guidance on when to use list_courses versus get_course for a single course, nor any note about when archived/provisioned states should be requested. Adequate but leaves selection logic to inference.

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