Full single-pool dossier from Barker's index by pool_uid: all APY components (percent unit), TVL, terms, execution capability, reward breakdown. Use after barker_defi_vaults / barker_yield_advisor to inspect one pool. (paid: $0.005 per call via x402)
| Name | Required | Description | Default |
|---|---|---|---|
| pool_uid | Yes | Pool uid from list tools |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden for behavioral disclosure. It mentions the paid cost ($0.005 per call) and lists informational data fields, but it does not explicitly state that the tool is read-only, what happens with an invalid pool_uid, or any authorization requirements. The term 'dossier' implies safety but this is not explicit.
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 two sentences, front-loaded with purpose, then usage, then pricing. Every sentence adds distinct value with no redundancy or fluff.
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?
The description covers what the tool does, the data it returns, the workflow context, and the cost. It does not mention error handling or pagination, but for a single-parameter detail tool with no output schema, this is largely sufficient. The enumerated return components compensate for the lack of an output schema.
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?
The input schema has 100% coverage with a clear description of pool_uid ('Pool uid from list tools'). The tool description reinforces the source by saying 'Use after barker_defi_vaults / barker_yield_advisor,' but adds no additional format or constraint details. Baseline 3 is appropriate given the schema already handles parameter documentation.
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 provides a 'Full single-pool dossier' with specific components (APY components, TVL, terms, execution capability, reward breakdown). It distinguishes itself from sibling tools by specifying it inspects one pool after using list tools, making its purpose unmistakable.
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 explicitly says 'Use after barker_defi_vaults / barker_yield_advisor to inspect one pool,' providing clear workflow guidance. It does not explicitly mention when not to use it or compare to alternative detail tools such as barker_pool_history, so it stops short of a full 5.
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.
Each tool has a clear, distinct purpose: yield recommendation, pool listing, execution discovery, quoting, detail/history, market data, cross-chain routes, and position monitoring. No two tools overlap in functionality.
All tools follow the consistent pattern 'barker_<domain>_<action>' using snake_case. The naming is descriptive and predictable, making it easy for an agent to understand the purpose of each tool.
With 11 tools, the server covers the entire stablecoin yield workflow without being bloated. Each tool contributes to discovery, execution, monitoring, or market analysis, and none feel superfluous.
The tool set provides end-to-end coverage for stablecoin yield management: from discovery and analysis to execution and position monitoring. Missing features like batch position queries are outside the server's stated scope.
