zhihu_search

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds meaningful context by noting reliance on the current Chrome session (implying session/login requirements) and output normalization ('normalized results'). This goes beyond what annotations provide, with no contradictions.

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 that front-loads the action, contains no filler, and conveys the essential function efficiently. It is an example of under-specification, not verbosity.

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 tool has an output schema and strong annotations, so return values are covered. However, the description omits search_type options and offset behavior, and lacks any usage guidance. It is minimally viable but leaves gaps for a tool with 3 parameters and 0% schema coverage.

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 input schema has 0% description coverage for its three parameters, and the description itself does not explain keyword, offset, or search_type. The only parameter hint is the search_type enum's description in the schema, but the main description adds no meaning to any parameter, failing to compensate for low schema coverage.

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 uses the specific verb 'Search' with the resource 'Zhihu', and adds 'using the current Chrome session' and 'return normalized results' to clarify scope. This clearly distinguishes it from sibling search tools for other platforms like xhs_search and x_search.

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?

There is no explicit when-to-use or when-not-to-use statement, but 'Search Zhihu' unambiguously indicates the intended context, and 'using the current Chrome session' implies a prerequisite session dependency. No exclusions are given, so it is clear context without exclusions.

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