youtube_analytics_query

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

With no annotations, the description must carry behavioral disclosure. It discloses the live audience behavior for live streams, which is a specific behavioral trait. However, it omits broader behaviors such as authentication requirements, rate limits, or the fact that it is a read-only operation, leaving significant gaps in transparency.

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 two sentences with no redundancy. It front-loads 'Unrestricted,' which immediately signals the tool's core value, and the second sentence adds a relevant behavioral nuance. Every word earns its place, making it highly concise and well-structured.

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 high-complexity tool with 15 parameters, no output schema, and no annotations. The description is too sparse to guide an agent through constructing valid queries or understanding result formats. It lacks information about return types, handling large outputs (though outputPath is in the schema), or common pitfalls, making it incomplete for effective use.

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 53%, which is moderate, so the baseline is 3. The description adds marginal value by indicating the tool accepts 'any metrics/dimensions/filters/sort,' which relates to several parameters, but it does not elaborate on syntax or formats. It does not compensate for the undocumented parameters that lack schema-level 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 clearly identifies the tool as 'Unrestricted YouTube Analytics reports.query' with 'any metrics/dimensions/filters/sort the API accepts,' which precisely defines its function. It distinguishes itself from siblings only by the term 'unrestricted' but does not explicitly name the restricted alternatives, so it is clear but not fully differentiated.

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 no explicit guidance on when to choose this tool over its siblings. It mentions the 'since published' window nuance but does not state criteria like 'use this for arbitrary queries or when you need full flexibility.' Without this, an agent lacks direction on optimal selection.

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