search_content

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention that this is a read-only operation, whether results are paginated, or any limitations (e.g., no results handling). It only lists search capabilities, lacking depth in behavioral context.

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 long and front-loaded with the core function. Every word adds value, and there is no redundant or filler content.

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?

For a 6-parameter search tool with no output schema, the description is adequate but has gaps. It does not mention pagination, response format, or that region/language filters exist in the schema, which an agent might need for effective invocation.

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 repeats what the schema already provides (e.g., search by title, actor, director, genre, keywords; Chinese and English support) without adding new meaning beyond the parameter 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 the tool searches for specific content types (dramas, variety shows, anime, movies, documentaries) on WeTV and Tencent Video. It uses the specific verb 'search' and lists search dimensions (title, actor, director, genre, keywords), distinguishing it from sibling tools like get_trending and get_content_detail.

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?

While the description implies this tool is for searching specific content, it does not explicitly state when to use it versus alternatives such as get_trending for discovery. No exclusions or preferred contexts are mentioned, but the purpose is self-evident.

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