get_videos

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves videos for a search query but lacks details on behavioral traits such as authentication needs, rate limits, pagination, or what happens if no results are found. This is a significant gap for a tool with no annotation coverage.

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 appropriately sized and front-loaded with the main purpose in the first sentence, followed by a structured 'Args' section. It avoids unnecessary details, though the formatting could be slightly more polished for clarity.

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 the complexity of video retrieval, lack of annotations, no output schema, and low schema description coverage, the description is incomplete. It doesn't explain return values, error handling, or how results are structured, leaving key contextual gaps for effective tool 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?

The description includes an 'Args' section that lists and briefly describes the two parameters ('search' and 'max_results'), adding meaning beyond the input schema which has 0% description coverage. However, it doesn't provide details like expected formats for 'search' or constraints for 'max_results', only partially compensating for the schema gap.

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's purpose with a specific verb ('Get') and resource ('videos'), and specifies it's for a search query. However, it doesn't differentiate from sibling tools like 'get_trending_videos_tool' or 'get_related_videos_tool' which might also retrieve videos under different conditions.

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 guidance on when to use this tool versus alternatives like 'get_trending_videos_tool' or 'get_related_videos_tool'. It mentions a search query but doesn't specify contexts where this is preferred over other video retrieval tools, leaving usage unclear.

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