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 non-destructive, non-network-bound profile is covered. The description adds only a partial return hint (差异基因、富集结果) and says nothing about runtime expectations, data download behavior, or whether intermediate results are persisted for a three-stage pipeline.

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 USE WHEN / ALIASES / RETURNS layout is front-loaded and easy to scan, with no redundancy. The bilingual aliases block is somewhat noisy but serves retrieval, so the wording largely earns its place.

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 composite three-stage pipeline with no output schema, the definition is thin: it does not say what artifacts come back beyond '差异基因、富集结果', omitting the immune infiltration output that the USE WHEN clause promises. An agent can invoke it but cannot predict runtime, intermediate files, or defaulted parameters.

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 geo_id, species, pval_cutoff and logfc_cutoff all documented inline, so the baseline of 3 applies. The description adds no semantics beyond the schema — no defaults for species or the cutoffs, and no statement that the cutoffs govern the DEG stage specifically.

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 states a specific resource (a GEO accession) and enumerates the pipeline stages: DEG → enrichment → immune infiltration, so an agent knows this is an end-to-end multi-step analysis rather than a single computation. However, it never distinguishes itself from related siblings such as differential_expression, rnaseq_deg, or go_kegg_enrichment, which perform individual stages of the same workflow.

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?

"USE WHEN: end-to-end on a GEO accession" gives a concrete selection condition that separates whole-pipeline runs from single-step tools. It stops short of stating when NOT to use it (e.g. when only DEGs are wanted, use differential_expression instead) and names no alternative sibling explicitly.

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