classroom_list_assignments

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds concrete behavior beyond that: 'Returns one page as {items, nextPageToken}; continue until nextPageToken is null.' This gives the agent the pagination contract and confirms a read-only listing operation. No contradiction 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 two sentences, front-loaded with the core verb and resource, then adds filtering and pagination details. Every sentence contributes meaningful information and there is no filler.

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 paginated list endpoint, the description does provide the return shape and continuation rule, which is important since no output schema exists. However, it omits the meaning of fullData and pageSize, and it does not explain what an 'item' contains. This makes the description adequate but not fully 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?

Schema description coverage is only 20%, so the description must compensate. It mentions 'Supports filtering by state' for courseWorkStates and implies pageToken via the pagination note, but it does not explain fullData, pageSize, or the semantics of courseId beyond the obvious. With 5 parameters and most undocumented, this is a clear 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 states a specific action and resource: 'List coursework (assignments/questions) for a course.' This clearly separates it from sibling tools like classroom_get_assignment, classroom_create_assignment, and classroom_patch_assignment, even though it does not name them explicitly. 'Supports filtering by state' adds useful scoping.

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 implies when to use the tool: when listing coursework for a course and optionally filtering by state. It also explains how pagination works, which is useful. However, it does not explicitly contrast with alternatives such as classroom_get_assignment for a single item or list tools for other resource types.

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