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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. Beyond that the description adds nothing behavioral: the 'RETURNS: 代谢物通路富集' line just restates the tool name, and it never discloses the reference database, statistical model behind the FDR threshold, or required identifier format (no organism/ID-type parameter exists, which is a notable omission the description does not explain).

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 template is front-loaded and scannable, so it is not verbose in absolute terms. However, the title is duplicated verbatim at the start, the ALIASES block is mostly search-bait, and the RETURNS field consumes space without conveying information.

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 two-parameter, non-destructive analysis tool with full schema coverage and annotations, the agent can decide when to call it. What is still missing is input-format guidance for the metabolite list and any indication of what the enrichment result contains, which matters because there is no output schema to fall back on.

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 both parameters (代谢物列表, FDR 阈值) documented inline, so the schema carries the parameter burden and baseline 3 applies. The description adds no meaning beyond it — notably it never says what identifier system the metabolite list should use, which is the one thing the schema does not settle.

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 names a specific verb+resource: 'pathway enrichment' over 'metabolites', which distinguishes it from the protein and gene/KEGG enrichment siblings (protein_enrichment, go_kegg_enrichment) by analyte type. It does not explicitly name those siblings or state the contrast, so it stops short of a 5.

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: pathway enrichment for differential metabolites' gives a clear triggering context, and the alias list (差异代谢物, KEGG代谢) helps match user phrasing. There is no when-not guidance and no pointer to the neighboring metabolite tools (metabolite_volcano, metabolite_heatmap, metabolite_pca), which the agent must route between on its own.

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