List videos

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

Beyond the annotations, which already mark this as a safe read-only operation, the description discloses important behavior: one video per Classroom lesson with a video, newest-post feed scanning, uploaded versus linked video shapes, and locked_courses listing courses whose videos are withheld. This is substantial behavioral context for an agent deciding what this call returns.

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 front-loaded with the core purpose and then packs useful details about ordering, feed scanning, video types, and locked courses into a compact form. Every sentence contributes actionable information, with no redundant restatement of the tool name.

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 read-only list tool with no output schema, the description provides enough context about what is returned, how feed scanning works, how uploaded and linked videos differ, and what happens with locked courses. Combined with the annotations and fully described schema, an agent has what it needs to call this correctly.

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 100%, so the schema already documents group, where, and post_pages, including defaults and enum values. The description adds some useful framing around post_pages and where, but most parameter meaning is already present in structured fields, so this meets the baseline rather than adding much beyond it.

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 and resource: it lists videos in a group's Classroom lessons and feed posts, distinguishing uploaded from linked videos. It also explicitly points to get_video_transcript for transcript retrieval, so an agent can distinguish this from the related transcript tool without opening 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 description clearly explains the scope: Classroom lesson videos in course order plus videos from the newest feed posts, with post_pages controlling feed scanning. It names get_video_transcript as the follow-up tool for uploaded videos, though it does not explicitly cover when to prefer list_posts or list_courses instead.

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