get_youtube_liked_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 discloses the key access requirement (OAuth2 token) for what is otherwise a read-only operation. It does not mention pagination, output shape, or failure behavior, but these are less critical for a simple getter.

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 one short, well-structured sentence with no filler. It front-loads the operation and resource, then states the crucial auth caveat, making every word earn its place.

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?

This is a simple two-parameter getter with an output schema, so the lack of return-format documentation is acceptable. The main gap is the tension between the stated token requirement and the schema's optional access_token with a null default, with no guidance on behavior when the token is omitted.

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 0%, so the description must compensate for the missing parameter documentation. It adds meaning for access_token by noting it is an OAuth2 requirement, but it says nothing about max_results, leaving its semantics to be inferred entirely from the parameter name.

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 ('Get') and a specific resource ('user's liked YouTube videos'), making the tool's function immediately clear. It is also distinguishable from sibling tools like get_youtube_subscriptions or get_youtube_playlists without needing to open schemas.

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 provides a relevant precondition — the OAuth2 access token — which implies the tool should be used after authentication. However, it gives no explicit guidance on when to prefer this over sibling tools or what to do if the token is missing or expired, such as using token-status or refresh helpers.

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