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 elsewhere. Beyond that the description only adds the fragment '研究方案正文', which hints at output content but says nothing about generation behavior, length, determinism, or what inputs are ignored. It does not contradict the annotations, but it contributes almost no behavioral context.

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 wasted marketing language, but it is not front-loaded prose — it repeats the tool title verbatim as the first fragment and then stacks two more fragments without connectors. Terseness here reflects under-specification rather than discipline.

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?

This is a generative tool with no output schema, so the description carries the burden of describing what comes back. Instead it offers only '研究方案正文', leaving the agent without guidance on output scope, structure, or how the three optional inputs interact. For a generation tool in a crowded sibling set, this is thin.

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 type, title and prompt are all documented in the schema itself. The description's mention of sample size, statistical plan and ethics points vaguely signals what the 'prompt' should contain, but adds no format, length, or constraint details beyond the schema. Baseline 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?

The description does state a verb+resource (生成研究方案 / generate a research protocol) and narrows the scope with the parenthetical '(含样本量、统计计划、伦理要点)'. However it is written as three unconnected fragments with no sentence structure, and it gives no differentiation from siblings that plausibly overlap, such as act_topic_research_plan, act_experiment_plan, or study_design_advisor. The purpose is inferable but not sharply drawn.

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 clause '用户要一份完整研究方案' gives an implicit trigger condition, but there is no explicit when-to-use/when-not guidance and no named alternative. With this many closely related design/writing siblings in the tool list, the agent has no basis in the description for choosing this tool over act_topic_research_plan or act_experiment_plan.

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