get_indexed_videos

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

No annotations are present, so the description carries full burden. It discloses that the tool retrieves indexed video IDs with optional filtering and details the return dictionary structure. However, it does not mention potential performance implications or that it only returns indexed videos, not all videos.

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 and well-structured, with a brief intro followed by clearly labeled Args and Returns sections. Every sentence adds value, and the information is front-loaded. No wasted words.

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?

The description covers the two optional parameters and details the return dictionary fields. An output schema exists, reducing burden on the description for return values. Minor gap: it could clarify that only indexed videos are returned and that content_type filter values are examples, not an enum.

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%, but the description explicitly explains both parameters: channel_id as an optional filter by YouTube channel ID, and content_type as an optional filter with example values 'transcript' or 'comment'. This adds significant meaning beyond the schema's property definitions.

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 'Get list of videos that have been indexed for semantic search,' specifying verb (get), resource (indexed videos), and scope (for semantic search). It effectively distinguishes from sibling tools like semantic_search_* which perform searches rather than listing.

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 says 'Useful for understanding what content is available,' implying when to use, but lacks explicit guidance on when not to use or comparisons with alternative tools. No exclusions or context about prerequisites are provided.

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