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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered without the description. The description contributes one extra behavioral fact — that results are restricted to the published corpus ('已发布口径') — but says nothing about ranking, matching semantics, or pagination.

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 content-type enumeration is front-loaded and useful, but the English sentence is a straight translation of the Chinese with no added information, so roughly half the text is redundant for a bilingual reader.

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 simple three-parameter read-only search with no output schema, the definition covers what the tool searches over but not what a result contains or how matches are ranked. Adequate but with clear gaps for an agent deciding whether a hit is relevant.

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%: query (keyword in title or summary, 2-80 chars), lang (enum zh/en), and limit (1-10) are all documented in the schema. The description adds no parameter-level detail beyond that, so the baseline of 3 applies.

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?

States a specific verb (搜索/Search) and resource (SVTR 原创研究文章) and enumerates the content types covered (Thesis, Profile, Radar, 周报), which lets an agent tell this apart from search_organizations. It stops short of explicitly naming the sibling it differs from, so it lands at 4 rather than 5.

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 when-to-use or when-not-to-use guidance and no alternative tool is named, despite search_organizations being an obvious near-neighbor. The only scoping signal is '已发布口径' (published only), which is a filter, not usage guidance.

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