wormbase_gene

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns gene information (a behavioral trait) but does not explicitly state whether the operation is read-only or any side effects. As a 'Get' tool, this is implied, but not clearly stated.

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 concise with two sentences, one in English and one in Chinese. The information is front-loaded, but the repetition across languages is minor redundancy. It is still efficient and easy to scan.

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 one-parameter lookup tool with an output schema, the description is complete: it states the purpose, the input format, and the type of returned data. Nothing essential is missing for an agent to invoke it correctly.

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 has zero description coverage for gene_id. The description compensates by explaining the expected format (WormBase ID) and providing an example (WBGene00000001), adding meaningful context beyond the bare schema.

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 states a specific verb ('Get'), a precise resource ('C. elegans gene'), and the method ('by WormBase ID'). It also lists the returned data types (name, symbol, chromosome location, functional annotation, sequence information), making it clearly distinct from broader search tools like wormbase_search.

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 clear context: use this tool when you have a WormBase ID for a C. elegans gene. It implies the appropriate scenario but does not explicitly mention alternatives or when-not-to-use. Since the tool is specialized, this is adequate.

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