list_my_uploads

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 sign-in requirement and ordering, but does not mention pagination behavior, rate limits, or what happens if the user is not signed in. For a read-only list operation, the lack of explicit safety disclosure is a gap.

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 short sentences with no filler. The core action and ordering are front-loaded, and the sign-in requirement is stated efficiently.

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 simple list tool with two optional parameters and no output schema, the description is mostly adequate. However, it lacks guidance on pagination behavior and error handling for the sign-in requirement, which an agent would need for robust invocation.

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 50%: max_results has a description ('1-50') but page_token has none. The description adds the 'newest first' ordering context, which helps interpret pagination, but it does not explain page_token semantics beyond what the schema provides. 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 states a specific verb ('List'), resource ('videos uploaded by the signed-in account'), and ordering ('newest first'). It clearly distinguishes from siblings like list_channel_uploads and search_videos, though it doesn't explicitly name them.

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 context: it is for the signed-in account's uploads, and it notes 'Requires sign-in.' It does not explicitly state when to use alternatives like list_channel_uploads or search_videos, but the scope is clear enough for an agent to infer.

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