ytptube_list_tasks

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the agent knows this is a safe read operation. The description adds the pagination behavior, which is useful, but it does not disclose details about ordering, default values, or the exact nature of what 'scheduled tasks' means beyond the name. No contradiction with annotations.

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, front-loaded sentence that states the core action and key feature (pagination) without any redundancy. Every word earns 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?

Given the low complexity (read-only list with two optional params) and strong annotations, the description is adequate but not comprehensive. It lacks explicit mention of what fields are returned, ordering, or any caveats about open world behavior, but these are partially covered by annotations and the simplicity of the tool.

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?

With schema description coverage at 0%, the description must compensate, but it only says 'with pagination'. While the parameter names 'page' and 'per_page' are self-explanatory, the description adds no details about how they work together, defaults, or edge cases. This is minimal compensation for the lack of schema descriptions.

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 scheduled tasks with pagination' uses a specific verb ('List') and a clear resource ('scheduled tasks'), which distinguishes it from sibling tools like list_history, list_archive, and live_queue. The addition of pagination further clarifies the tool's mode of operation.

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 the obvious use case of enumerating scheduled tasks, but it does not explicitly state when to use this tool versus alternatives such as list_history or list_archive. No exclusion criteria or alternative tool names are provided, so the guidance is only implied.

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