token_metadataERC-20 metadata.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | ||
| contract | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| logo | No | Token logo URL | |
| name | No | Token name | |
| symbol | No | Token symbol | |
| decimals | No | Token decimal places |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnly, idempotent, non-destructive, and openWorld, which already convey safety. The description adds the ERC-20 scope, clarifying that the tool only applies to ERC-20 tokens, a behavioral constraint not present in annotations. However, no additional behavioral details like return format or limitations are disclosed.
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 extremely short, but it is under-specified rather than concise. A single fragment does not earn its place; it sacrifices clarity and provides minimal information, similar to the 'Process' example.
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?
Despite having an output schema and rich annotations, the description fails to state the operation or when to use the tool. With siblings like token_balances and token_allowance, the tool could be easily confused. The description is insufficient for an agent to select and invoke this tool correctly without further inference.
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%, and the description provides zero parameter-level information. The parameter names 'contract' and 'chain' are somewhat self-explanatory, but the agent is left guessing expected formats (e.g., whether chain is a chain name or ID, what contract address format is required).
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 is a fragment 'ERC-20 metadata.' with no verb or action. It restates the title with a token standard, but does not clearly state whether it retrieves, creates, or updates metadata. While it hints at a distinction from NFT metadata, it lacks a specific operation.
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 on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or sibling tools, leaving the agent without context for tool selection.
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.
Several tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta (currently described as identical), ask_pipeworx_grounded, and deep_research all serve question-answering/research, and the six Polymarket tools heavily overlap in finding and evaluating trading edges. Individual descriptions are detailed, but an agent could easily route to the wrong variant.
The set mixes conventions: Pipeworx tools mostly use verb_noun (ask_pipeworx, compare_entities, resolve_entity), but memory tools are bare verbs (remember, recall, forget), and the Ethereum tools are inconsistent (nft_metadata vs nfts_owned vs nft_owners, token_balances vs token_allowance). The lack of a uniform pattern makes the surface harder to predict.
At 40 tools, the server is oversized for the apparent core purpose of an Alchemy Ethereum interface. There is also significant redundancy: multiple ask/deep-research entry points and a dense suite of Polymarket analysis tools add bulk that could be consolidated.
The Ethereum side is mostly read-only convenience wrappers (NFTs, tokens, asset transfers) plus a generic eth_call catch-all, but lacks dedicated transaction sending, block/transaction detail, logs, or ENS conveniences. The rest of the tool surface is a sprawling collection of unrelated data-research, memory, and subscription features, making the overall implied domain incoherent and likely to leave obvious gaps for users expecting a focused Ethereum server.