export_gene_list

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 only mentions 'export' without disclosing output behavior, file formats, side effects, or permissions. This lack of transparency makes it impossible for an agent to predict the tool's behavior.

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, which is concise, but it is under-specified. It does not provide enough information to be considered appropriately sized; it is more of a placeholder than a useful description.

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 lack of annotations, zero description coverage, and multiple parameters, the description is grossly inadequate. It does not explain the concept of exporting, available formats, or how the output is structured, even though an output schema exists. This tool would be nearly impossible to invoke correctly based solely on the description.

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 three parameters, but schema description coverage is 0% and the tool description does not explain any of them. The parameter names (fields, format, gene_ids) are self-explanatory to some extent, but the description adds no meaning beyond the schema, especially for 'fields' and 'format'.

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 verb and resource ('Export gene data') but is vague about what 'export' means and what 'various formats' includes. It does not distinguish from sibling tools such as get_genes_batch or query_genes, which also handle gene data.

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?

No guidance is provided about when to use this tool versus alternatives. The description gives no context for when exporting is appropriate or what differentiates it from querying or batch retrieval tools.

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