youtube.video.performance_snapshot

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

With no annotations provided, the description carries full burden for behavioral disclosure. It lists the returned metrics but does not state whether the tool is read-only, idempotent, requires auth, has rate limits, or any side effects. This is a significant gap for a tool without 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 sentence that lists the output metrics efficiently. Every word contributes to understanding the tool's purpose. No unnecessary information.

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 no output schema, the description should clarify the nature of 'packaging metrics' and the output format. The tool is simple with one parameter, but the description lacks enough detail to fully understand what is returned, especially for packaging metrics.

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. It only mentions 'video' without explaining the expected format (e.g., ID, URL). No additional meaning beyond the parameter name is provided.

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 the tool returns views, engagement rate, views per day, and packaging metrics for a video. It uses a specific verb 'return' and identifies the resource 'video'. However, it does not explicitly differentiate from siblings like 'get_details' or 'batch_get_details', which also return video metrics.

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?

No guidance on when to use this tool versus siblings. It does not specify prerequisites, ideal conditions, or when not to use it. The agent must infer from the description that it's for a performance snapshot, but no exclusions or alternatives are mentioned.

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