get_experimentGet metadata for a single EBI Expression Atlas experiment by accession (e.g. "E-MTAB-4045"). Returns accession, description, species, type, assay count, and experimental factors.
| Name | Required | Description | Default |
|---|---|---|---|
| accession | Yes | Experiment accession, e.g. "E-MTAB-4045", "E-GEOD-61857". |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, revealing safe, read-only behavior. The description adds valuable detail on returned fields (accession, description, species, type, assay count, experimental factors), enhancing transparency beyond annotations.
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, well-structured sentence that front-loads the action and purpose. Every word is necessary, making it concise and easy to parse.
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 simple retrieval tool with no output schema, the description fully covers what it does and returns. Combined with the annotations, it provides complete information for agent 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?
Schema coverage is 100% with a clear description of the 'accession' parameter. The description adds context by specifying the tool works for EBI Expression Atlas experiments and provides example accessions, which helps agents understand the parameter's format and scope.
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 'Get metadata for a single EBI Expression Atlas experiment by accession', specifying the verb, resource, and scope. It distinguishes from sibling 'search_experiments' by focusing on a single experiment, making the tool's purpose unambiguous.
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 for when to use (by accession for a single experiment) but does not explicitly state when not to use or mention alternatives. Given the simplicity, agents can infer usage, but explicit guidance is slightly lacking.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have overlapping purposes (e.g., multiple Polymarket tools, multiple company information tools), but descriptions help distinguish them. However, the variety of domains (brand monitoring, betting, package scanning, memory, etc.) can confuse an agent.
Tool names have no consistent naming pattern: some are verb_noun (validate_claim), some are noun_verb (bet_research), some are compound (ai_visibility_check), and some are single word (forget). This makes it hard to predict tool names.
28 tools is high, and the set spans many unrelated domains (brand visibility, SEC/FDA data, Polymarket, npm packages, memory, etc.) while the server is named 'Expression Atlas' with only 2 tools related to that purpose. The tool count feels excessive and unfocused.
For a server named 'Expression Atlas', only two tools (get_experiment, search_experiments) cover the domain. There are no tools for submitting, updating, or deleting experiments, nor any for data visualization. The surface is severely incomplete.