toutiao_search_works

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

The description discloses the real-time nature and pagination behavior (offset starts at 0, increments by 1 per page). However, with no annotations, it fails to disclose other important behavioral traits such as authentication requirements, rate limits, or whether the tool is read-only. The disclosure is minimal.

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 extremely concise, consisting of a single sentence plus parameter hints. There is no wasted text, and every element serves a purpose.

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 basic usage and pagination, but lacks context about the scope of the search (e.g., what types of content are included), potential limitations, or how to interpret results. The existence of an output schema partially compensates for missing return value details, but the overall description feels sparse for a tool with many siblings.

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?

With 0% schema description coverage, the description provides essential meaning for both parameters: it clarifies that 'keyword' is required and 'offset' is a pagination offset starting at 0 and incrementing by 1 per page. This adds value beyond the raw schema, but does not elaborate on the format or expected values of the keyword.

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 explicitly states '搜索今日头条内容（实时）' (Search Toutiao content (real-time)), clearly identifying the action (search) and resource (Toutiao content). It is not a tautology and distinguishes from sibling tools like toutiao_get_work, though it does not explicitly contrast with other platform 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 provides no guidance on when to use this tool versus other search tools for different platforms. There is no mention of prerequisites, alternatives, or scenarios where this tool is preferred. This is a significant gap given the large number of sibling search tools.

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