gas_feesFetch estimated on-chain gas fees from Gemini for a symbol (e.g. ethusd): fee amount and unit. Use before estimating ETH withdrawal costs.
| Name | Required | Description | Default |
|---|---|---|---|
| symbol | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| fee | No | Estimated gas fee | |
| surgeGasPrice | No | Surge gas price |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint false. The description adds that it returns fee amount and unit, which is consistent and adds useful context. No contradictions or missing behavioral traits for a read-only operation.
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?
Two sentences cover purpose, resource, output, and usage guidance with no redundancy. Every sentence adds value and the description is front-loaded with the core action.
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 single parameter, presence of an output schema, and rich annotations, the description is complete enough. It explains what the tool does, what it returns, and when to use it, satisfying all needs for effective 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 description coverage is 0%, but the description provides an example ('ethusd') and context ('for a symbol'), adding meaning beyond the schema's bare type string. However, it does not fully specify the expected format or possible values, so it partially compensates.
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 tool fetches estimated on-chain gas fees from Gemini for a symbol, specifying the action (fetch), resource (gas fees), and source (Gemini). It distinguishes from sibling tools which are unrelated.
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 a specific use case: 'Use before estimating ETH withdrawal costs.' This gives clear context, but it does not explicitly mention when not to use or name alternatives, which is acceptable for a simple tool.
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.