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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful scope detail by naming the external authorities queried, but it does not disclose rate limits, authentication needs, pagination, or other behavioral traits 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?

A single front-loaded sentence with the purpose first and the source list second. Every element earns its place by scoping the tool's data coverage, with no filler or repetition.

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?

The tool has an output schema and 100% schema description coverage, so the description need not explain return values or parameter details. It adequately defines the domain and sources, but lacks explicit sibling-routing guidance, leaving a small completeness gap.

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%, so the schema already documents source, query, limit, _files, and _subject in detail. The description names the covered sources, which aligns with the source enum, but adds no syntax or format guidance beyond what the schema provides, making the baseline 3 appropriate.

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?

States a specific verb ('Look up') and resource ('omics and regulation records'), then enumerates concrete authorities including GEO, ArrayExpress, PRIDE, MetaboLights, MGnify, ENCODE, JASPAR, and UniBind. This gives an agent a precise domain and distinguishes it from other lookup_* siblings that retrieve genes, proteins, compounds, or variants.

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 description implies usage by listing the omics and regulation sources it covers, but it does not explicitly say when to choose this tool over alternatives such as lookup_gene or search_records. There is no when-not guidance or named sibling alternative, so usage is only inferred from the source scope.

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