Atlas metadata: release, DOI, assembly, variant/breed counts, scope banner, and the RPC catalog.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Describes returned metadata items but does not disclose any behavioral traits (e.g., read-only nature, rate limits, or caching). Behavior is simple (parameter-less, read-only) but not explicitly 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?
Single sentence listing key metadata items. Front-loaded with purpose. No wasted words.
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?
Tool is simple (no parameters) and has an output schema. Description sufficiently enumerates the type of data returned, making it complete for an overview tool.
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?
No parameters exist, so schema coverage is 100%. Baseline score of 4 applies; description does not need to add parameter meaning.
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?
Description states specific verb+resource: returns Atlas metadata including release, DOI, assembly, variant/breed counts, scope banner, and RPC catalog. Clearly distinguishes from sibling query tools which provide specific data lookups.
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?
Lists what the tool returns, implying use for a general metadata overview. No explicit guidance on when to use or not use versus alternatives; agent must infer from sibling list and context.
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.
Tools are mostly distinct with clear purposes, but some overlap exists between disease-related tools (disease_lookup vs disease_links) and between ask and ask_the_graph. Descriptions help differentiate, but an agent might still misselect.
Naming patterns are inconsistent: some tools use verb_noun (ask, search_diseases), others use noun_noun (breed_similarity, disease_bridge), and some use descriptive phrases. No consistent convention observed.
18 tools is well-scoped for a canine genetics knowledge base. Each tool serves a distinct function covering breed, disease, variant, and query capabilities without being overwhelming.
The tool set covers all major aspects of the domain: breed profiles, disease lookup with links, variant querying, semantic search, and metadata. No obvious gaps for the stated educational purpose.
