List my YouTube videos

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

No annotations are provided, so the description carries the full burden. It states the operation is a read/list, but it does not disclose pagination behavior, default ordering, whether it returns only published videos, or any rate limits. The description adds minimal behavioral context beyond the tool name and title.

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 a single short sentence that is front-loaded and to the point. It earns its place by stating the core function, though it could add a bit more context without becoming verbose.

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 list tool with no output schema and no annotations, the description is thin. It does not mention what the response contains (e.g., video IDs, titles, thumbnails), pagination, or how the account parameter works. An agent would need to infer these details from the schema and sibling tools.

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 both parameters (account and maxResults). The description adds no additional meaning beyond what the schema provides, so the baseline 3 is appropriate.

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 'List the user's uploaded videos' clearly states the verb (list) and resource (the user's uploaded videos), which distinguishes it from sibling tools like google_youtube_search (searching videos) and google_youtube_get_video (getting a single video). It is concise and specific, though it doesn't explicitly contrast with siblings.

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 usage: it lists the authenticated user's own uploaded videos, which is distinct from search or playlist tools. However, it does not explicitly state when to use this tool versus alternatives like google_youtube_search or google_youtube_list_playlists, nor does it mention any prerequisites (e.g., authentication, account selection).

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