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 and scope profile is covered without the description. The description adds only a brief RETURNS line (pathway/disease/drug associations) and the 'mechanism network' framing; it says nothing about data sources, association confidence, or whether openWorldHint=false means a bundled local knowledge base. Useful but thin beyond the annotations.

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?

Front-loaded with the purpose and a clear USE WHEN clause, then aliases and return summary, so an agent can skim it. The title is repeated verbatim in Chinese and the alias list is long and partly redundant (e.g. 'network', 'gene pathway'), which is mild padding rather than noise.

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 single-parameter, read-only lookup with no output schema, the definition covers what it does, when to call it, and roughly what comes back. It is complete enough to invoke correctly, with only the return structure and knowledge-base scope left implicit.

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?

There is a single required parameter, 'genes', documented at 100% schema coverage, so the schema carries the burden and the baseline is 3. The description reinforces the gene-list input but adds no detail on list size, gene ID format, species, or whether duplicates/unknown symbols are tolerated.

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 gives a concrete verb and resource chain: from a gene list, find pathway/disease/drug associations and build a mechanism network. That is far more specific than the tool name alone, and the 'network' framing separates it from plain enrichment tools. It stops short of naming a specific sibling it is not (e.g. go_kegg_enrichment or ppi_network), so it lands at 4.

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: from a gene list...' clause states the trigger condition explicitly, which is exactly the kind of context an agent needs for routing. There are no exclusions, prerequisites, or named alternatives, so it is not a 5.

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