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

Annotations already declare readOnly, idempotent, and closed-world behavior, so safety is covered. The description adds the meaningful behavioral detail that matching is by name or synonym, but says nothing about ranking, fuzzy matching, or what happens with partial/ambiguous names.

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 sentence that front-loads the verb and scope with zero filler. Nothing could be removed without losing 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?

With no output schema, the description should explain what a result looks like (entity ids? scores? types?) but omits return shape entirely, and also omits pagination/limit behavior. For a search tool usable as an entry point, that is a real 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 coverage is only 67% — 'limit' has no schema description at all and 'type' is only exemplified, not enumerated. The description adds no parameter meaning (no valid type values, no limit semantics, no query-matching rules), so it fails to compensate for the gap.

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 (Find) plus the resource types it searches (genes/proteins, complexes, drugs, diseases, processes, nutrients, outcomes) and the matching basis (name or synonym). This clearly separates it from siblings like get_entity (id lookup) and search_studies (different corpus), though it never names an alternative explicitly.

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?

There is no when-to-use guidance, no mention of prerequisites, and no routing to alternatives such as get_entity once an entity is known. Usage is only implied by 'Find ... by name or synonym'.

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