List Course Materials (Lessons)

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds useful semantic scope by clarifying it returns CourseWorkMaterials rather than assignments, but it does not disclose additional operational behavior such as pagination behavior, auth requirements, or list completeness. It is not contradicted by any annotation.

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 core distinction is front-loaded in a single, clear sentence. The Args and Returns sections are compact and scannable, and every part earns its place. There is mild duplication with the input schema, but no filler or unnecessary prose.

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?

Since there is no output schema, the description appropriately lists the returned fields in the Returns section. It covers all parameters, the output format options, and the material type scope. Minor gaps remain around pagination behavior and any auth or error conditions, but the annotations already cover the read-only and idempotent nature of the operation.

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 75%, and the description mostly restates what the schema already provides. It adds minor clarification with 'Restrict to one topic' for topic_id and fills in the missing schema description for limit with 'Max items 1-200 (default 50)', but most parameter meaning is already present in the schema. This adds some value but does not go beyond a baseline level.

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 a specific verb and resource: 'List CourseWorkMaterials'. It clearly distinguishes these from assignments, which immediately separates this tool from sibling tools like classroom_list_coursework. The phrase 'posted reading/lesson materials' and 'what teachers typically use for lessons and resources' removes any ambiguity about the tool's purpose.

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 contextual guidance by stating these are materials that are NOT assignments, which tells an agent not to use this tool when the goal is assignments. It does not explicitly name sibling alternatives such as classroom_list_coursework or classroom_list_announcements, so it falls just short of full explicit routing guidance.

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