get_gene_orthologs

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

With no annotations available, the description must fully disclose behavioral traits, but it only states the basic function. It does not mention return behavior, filtering, side effects, or any other operational characteristics, offering insufficient behavioral transparency.

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 a single short sentence with no redundant wording, achieving high efficiency. However, it lacks any additional structure or detail, making it appropriately concise but perhaps too sparse for the tool's complexity.

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 three parameters, no annotations, and no parameter descriptions, yet the description only provides a high-level summary. It does not explain how to use the parameters or what output to expect, though an output schema is present. This is inadequate for reliable invocation.

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 schema has zero descriptions for its three parameters. The description says 'across species', which loosely implies the 'target_species' parameter, but it does not explain 'sources' or the relationship between parameters. This minimal compensation does not adequately cover the missing semantic information.

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 'Get' and the resource 'orthologs across species', indicating a read operation to retrieve orthologous genes across species. However, it does not explicitly distinguish from the sibling tool 'query_homologous_genes', which could be similar, so it is not fully differentiated.

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 no guidance on when to use this tool versus alternatives like 'query_homologous_genes' or 'query_genes'. It does not mention any exclusions, prerequisites, or context, leaving the agent without direction on tool selection.

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