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 nothing beyond them: no statement of what the tool returns, what the generated protocol looks like, latency, length limits, or what happens with an underspecified prompt.

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?

Short but fragmentary, repeating "实验方案" three times without structure or front-loaded guidance. Brevity here comes from under-specification rather than efficient editing, so it does not earn the length it has.

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 should convey output shape and constraints. Instead it leaves the return format, expected prompt granularity, and experiment_type vocabulary entirely unstated, which is insufficient for a two-parameter generation endpoint with many near-duplicate siblings.

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% (prompt = 实验需求描述, experiment_type = 实验类型), so the schema already binds both parameters. The description adds no meaning about how to phrase the prompt or which experiment_type values are accepted, so the baseline 3 applies rather than anything higher.

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 text mostly restates the title and tool name ("实验方案生成" ... "实验方案"), with only a thin scope hint: animal/cell experiment protocols for basic research. It never states a distinct verb+resource combination that separates it from design-oriented siblings such as act_design_generate, act_topic_research_plan, or study_design_advisor.

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 a use case but gives no explicit when-to-use/when-not-to-use rule and names no alternative. With dozens of overlapping design/writing siblings, an agent has no basis for routing between them from this description alone.

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