Search GW1 YouTube videos

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

No annotations are provided, so the description must carry full burden. It only mentions fetching from curated RSS feeds and default filtering, but does not disclose whether the operation is read-only, authentication requirements, rate limits, or the recency bound for 'recent' 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 two sentences, front-loaded with the main action, and contains no extraneous information. Every sentence adds value.

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?

Despite having 5 parameters and no output schema or annotations, the description fails to explain key aspects like the scope of sources, result limits, or how to specify custom source IDs. Significant contextual gaps remain for an AI to invoke the tool correctly.

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% (no descriptions on any of the 5 parameters). The description only vaguely references the 'query' parameter implicitly. No explanation is given for scope, maxTotal, sourceIds, or limitPerSource, leaving the agent without understanding parameter purpose.

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 fetches recent videos from curated public YouTube RSS feeds and provides default filtering behavior without a query. This distinguishes it from sibling tools like gw1_youtube_sources, which likely manages source curation, and other search tools.

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 implies that without a query the tool filters to Guild Wars 1/Reforged videos, suggesting query usage may broaden results. However, it lacks explicit guidance on when to use this tool versus alternatives like gw1_content_search or gw1_wiki_search, and does not mention when not to use it.

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