search

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

Annotations are missing, so the description must cover behavioral traits. It states the tool is for searching but does not mention if it's read-only, authentication needs, rate limits, or how empty queries behave (though schema parameter description mentions browsing newest). Lack of annotations means this is insufficient.

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 of 12 words, front-loaded with the action and resource. Every word earns its place with zero fluff.

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 simple tool with 5 documented parameters and an output schema, the description is mostly complete. It identifies the corpus and its scope. Minor gap: no mention of the curated nature or that it only covers recent videos, but schema covers parameter details.

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 100%, so the baseline is 3. The description does not add semantic value beyond the schema, but the schema itself is well-documented.

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 it searches a specific corpus (AI YouTube Digest) with per-video summaries from ~40 curated AI/coding channels. The action and resource are specific, and the sibling tool list_topics is complementary for topic labels, so distinction is clear.

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 list_topics, nor any prerequisites or conditions. The context is implied but not explicit.

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