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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is known and the bar for the description is lower. The description adds nothing beyond that: it does not say what corpus is compared against (notably, openWorldHint=false implies a closed/local literature pool, which the description never explains), what permissions or inputs are required, or what form the "对比结论" takes.

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, and the core action is front-loaded. But the three fragments are run together without punctuation and read as raw notes rather than a sentence, so the low word count comes partly from under-specification rather than tight writing.

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 read-only, two-parameter tool there is no output schema, so the description must convey what the agent gets back — instead it only gestures at "对比结论" without saying whether that is a novelty statement, a list of comparable papers, or a structured verdict. It also omits the source of the literature being compared against, which is the single most decision-relevant fact for this tool.

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% with only two parameters (title required, main_findings optional), so the schema already carries the parameter meaning. The description mentions "自己的发现", which loosely maps to main_findings, but adds no format, scope, or richness guidance beyond that.

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 a verb and resource (compare the user's findings against published literature to establish novelty), which is more than a restatement of the title, but the phrasing is telegraphic and fragmented ("对比结论" as a trailing noun phrase). It never distinguishes this from near-neighbours such as act_topic_novelty, act_pdf_local_compare, act_lit_digest, or literature_search_pmc, so an agent cannot tell which novelty-related tool 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?

"用户想知道自己的发现和已发表文献比新在哪" implies the triggering scenario (user wants to know how novel their findings are), which is genuine usage context. However there are no when-not conditions, no prerequisites (e.g. requires a written-up finding set), and no routing to alternatives among the many sibling literature/novelty tools.

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