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 by structured data. The description adds only a light return hint ('富集通路与 P 值'), and says nothing about the statistical procedure, multiple-testing correction, background gene set, or species assumptions, all of which materially affect interpretation of an enrichment result.

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 pipe-delimited layout is front-loaded with the actionable USE WHEN clause, which is good. However, the ALIASES line is keyword padding ('富集分析, 通路, 功能注释') that conveys no operational information, and the title is duplicated twice as the first segment and the title field.

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, single-required-parameter tool with no output schema, the description covers purpose and a rough return shape. It omits what an agent most needs before calling: expected gene identifier format (symbol vs. Entrez), organism scope, and how P values are adjusted, which are common failure points for enrichment 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%, and each of the three parameters (db_filter, gene_list, project_id) is already documented in the schema, including the GO_BP/GO_CC/GO_MF/KEGG vocabulary. The description mentions the gene list but adds no format or identifier-convention detail, so the 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 title line and the USE WHEN clause state a specific verb and resource: pathway enrichment (GO biological process / KEGG) over a supplied gene list. An agent can tell what it produces, but the description never distinguishes it from nearby siblings such as protein_enrichment, gene_pathway_disease, or metabolite_pathway, so the boundary is left to inference.

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 'USE WHEN: pathway enrichment for a gene list' clause gives a clear triggering condition, which is the main routing cue an agent needs. It stops short of exclusions or named alternatives, so 5 is not warranted.

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