youtube_reporting_list_reports

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

No annotations are provided, so the description carries the burden. It discloses report generation frequency and retention period, but does not mention authentication requirements, side effects, or that it returns only metadata. For a read-only list operation, this is adequate but not rich.

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 concise, front-loaded with the main purpose, and efficiently structured with an Args section. Every sentence earns its place—no filler or repetition.

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 one-parameter list tool with no output schema, the description covers the purpose, parameter source, and report availability window. It could mention that report IDs returned can be used with youtube_reporting_download, but the current description is largely complete for its complexity.

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 coverage is 0%, so the description compensates by explaining job_id as 'Job ID (from youtube_reporting_create_job or youtube_reporting_list_jobs)'. This adds valuable context beyond the schema's type-only definition, guiding where to obtain the parameter.

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 clearly states 'List available reports for a job' with a specific verb and resource. It distinguishes from sibling tools like youtube_reporting_list_jobs and youtube_reporting_list_types by focusing on reports for a given job.

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 usage context by noting reports are generated daily and available for 60 days, and it indicates job_id comes from youtube_reporting_create_job or youtube_reporting_list_jobs. While it doesn't explicitly mention alternatives, it implies when to use this tool for a specific job.

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