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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. However, the description does not clarify that this is a pure generation or summarization operation, does not say whether it returns text or a card object, and does not say what the card contains. With annotations carrying the safety story, the description adds almost nothing further.

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 tool's Chinese title is echoed twice, once as the title and once as the dangling trailing '摘要卡'. The middle sentence is the only one that carries information, so the definition reads as under-specified and repetitive rather than as a front-loaded statement of what the tool does. The first sentence and the trailing '摘要卡' could be removed without any loss.

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?

There is no output schema, so the description should explain what a '结构化摘要卡' contains, such as fields, format, or typical use for later literature workflows; instead, it does not do this. For a tool in a large literature and writing suite with no documented output, that is a real gap. The agent is left guessing the return shape and the required input depth.

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%, and each of the four parameters (title, source, abstract, external_id) has its own schema description. Therefore, the baseline of 3 applies. The description does not say whether 'abstract' is the raw input the card is generated from, or whether the 'title' parameter is the card's title or the paper's title. It therefore adds no meaning beyond the schema.

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 phrase '用户给一篇文献要生成结构化摘要卡' does state a verb and a resource: generate a structured abstract card from a paper. However, it never distinguishes this tool from the many siblings. For example, act_literature_compare, act_lit_systematic_review, act_pdf_pico, and act_pdf_review_outline all operate on literature as well. The final '摘要卡' merely repeats the title and adds no distinguishing information.

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 only usage signal is the implied trigger '用户给一篇文献', meaning the user supplies a paper. The description gives no when-to-use guidance, no when-not-to-use guidance, and no alternative tool it should route to, even though several literature tools exist. It does not state whether the tool requires a full text, an abstract, or just a title.

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