Find Drug-Gene-Disease Network

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds context about the graph traversal and store population, explaining that the tool is non-destructive and does not modify data. It also clarifies the resolution behavior for each seed type.

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 description is front-loaded with the main action and then elaborates on seed types and store population. It is well-structured and concise, though the second paragraph could be slightly more compact.

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?

Given the tool's complexity (2 parameters, output schema exists) and the presence of sibling tools, the description provides sufficient context for an agent to understand the tool's purpose, usage, and behavior. It covers seed resolution and data source, making it complete.

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?

The input schema already describes both parameters (seed and max_hops). The description adds context about seed resolution but does not add significant meaning beyond what the schema provides. Since schema coverage is effectively 100%, baseline score of 3 is 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?

The description clearly states the verb 'Traverse the local knowledge graph from a seed entity' and specifies the resource (local knowledge graph). It explains the behavior for different seed types (gene symbol, UniProt ID, MONDO disease ID), distinguishing it from sibling tools that may query specific entities.

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 provides explicit usage context: for a given seed type, it resolves to specific entities (proteins, variants, drugs). It also mentions the store is populated by curated data and explicit writes, but does not explicitly exclude sibling tools or provide when-not-to-use guidance.

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