getVideoComments

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

Annotations already declare readOnlyHint and idempotentHint, and the description confirms this by noting it's a retrieval operation. Additionally, it warns about increased API cost when setting maxReplies > 0, which is valuable beyond 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?

Three sentences with no unnecessary words. Front-loaded with purpose, followed by a critical warning, then a usage guideline. Every sentence serves a purpose.

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 5 parameters (all documented in schema), annotations covering read-only/idempotent, and no output schema, the description is fairly complete. It could mention the return format (e.g., list of comment objects), but the core information is present.

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 100%, so baseline is 3. The description adds a cost warning for maxReplies and notes default behavior, slightly increasing value. However, it doesn't elaborate on other parameters beyond what's in the schema.

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 'Retrieves comments for a video' with a specific verb and resource. It distinguishes from siblings like getVideoDetails or searchVideos by focusing on comments. The warning about maxReplies and default behavior further clarifies scope.

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?

Provides explicit guidance on when to use maxReplies ('only if you specifically need to analyze conversation threads') and defaults to top-level comments. Lacks explicit when-not-to-use compared to other tools, but the purpose is sufficiently distinct.

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