price_feedGemini crypto exchange — all listed pair prices in one snapshot: pair, price, 24h change percent. Use for cross-pair scan or fast latest-price across many tokens.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of items returned. | |
| items | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint true, and destructiveHint false. Description adds context about returning a snapshot of all pairs with specific fields, which is mildly informative 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?
Extremely concise: one sentence describing output structure and one sentence for use case. No wasted words, front-loaded with essential information.
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 tool has zero parameters and an output schema exists, the description fully explains the output fields and typical use cases. No additional information is needed for this simple 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; schema coverage is 100% trivially. Description adds meaning about the purpose of the snapshot for cross-pair scanning, which compensates for the lack of parameters.
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 clearly states the tool provides a snapshot of all Gemini crypto exchange listed pair prices including pair, price, and 24h change percent. It specifies the source and distinguishes itself from siblings like ticker or candles by focusing on cross-pair broad overview.
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?
Description explicitly states use cases: 'cross-pair scan or fast latest-price across many tokens.' It implies when to use but does not explicitly mention when not to use or list alternative tools.
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 serve overlapping research purposes (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim, entity_profile, compare_entities), which could confuse an agent. However, descriptions help differentiate them by use case (single vs multi-part, grounded vs standard, etc.). Some overlap remains.
Tool names mix patterns: some are verb_noun (ask_pipeworx, bet_research), others are noun_phrase (price_feed, recent_alerts) or adjective_noun (ticker_v2). No strong naming convention, but all use snake_case consistently, making them readable.
40 tools is on the high side for a single server, covering both Gemini exchange data and Pipeworx's broad knowledge tools. While each tool serves a purpose, the scope feels broad, and some tools could be separated into dedicated servers.
The Gemini exchange tools cover essential read-only data (order book, candles, ticker, trades), but lack order placement, likely intentionally. The Pipeworx tools provide extensive research capabilities across many domains, leaving few gaps for the stated purposes.