classroom_list_materials

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

Annotations already provide readOnlyHint and openWorldHint, but the description adds meaningful runtime behavior: it returns one page as {items, nextPageToken} and requires callers to continue until nextPageToken is null. This pagination contract is not available from the annotations or the sparse schema descriptions.

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 concise sentences with no filler. The first defines the tool's purpose and the second immediately provides the critical pagination contract, making the description easy to parse and act on.

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 gives a usable return shape and pagination loop, which is valuable given there is no output schema. However, it omits the optional filtering and verbosity controls such as courseWorkMaterialStates and fullData, leaving non-default usage under-specified.

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, but it does not. The description only implicitly mentions pageToken via nextPageToken and leaves fullData, pageSize, and courseWorkMaterialStates unexplained beyond their names.

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 verb, 'List', and a specific resource, 'non-graded materials for a course'. This clearly distinguishes the tool from sibling tools like classroom_list_assignments and classroom_list_announcements without needing to inspect the schema.

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 phrase 'non-graded materials' gives clear context for when the tool is appropriate and implicitly excludes graded assignments. However, it does not explicitly name alternatives or say when not to use it, stopping short of full routing guidance.

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