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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only the trailing fragment '综述文本', hinting at a text output, but says nothing about depth, length, whether it draws on real retrieved literature versus generating a draft, or what the four PICO-style inputs actually change in the result. Given openWorldHint=false, whether external search occurs is exactly the question an agent would need answered, and it is not.

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?

It is short with no filler, but it is a run of three unpunctuated fragments rather than a structured statement, and the most useful information (output is a review text) is buried at the end. Brevity here comes from under-specification rather than disciplined editing.

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 four-parameter tool with no output schema, the description should at minimum say what the returned review covers and how it differs from sibling review tools. Neither is present, leaving an agent to guess at scope and at the choice among many adjacent literature tools.

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 topic, question, population, and intervention are each documented in the schema. The description adds no meaning beyond those labels and never explains how the optional PICO fields alter the review. Baseline 3 applies when the schema carries the parameter burden.

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 names the resource (文献综述) and the trigger condition (用户要就一个题目做文献综述、研究现状梳理), so the general purpose is graspable. However, it never distinguishes this from close siblings such as act_lit_systematic_review, act_lit_digest, act_literature_compare, or act_topic_gaps, all of which sound like literature-review work. An agent cannot tell from the text alone which one to pick.

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 phrase '用户要就一个题目做文献综述' implies a usage context but states no explicit when-to-use rule, no when-not-to-use rule, and no alternative tool. With a dozen literature-related siblings in the list, the absence of any routing guidance is a real gap.

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