Neutral, verifiable value-accrual mechanics of $BOBAI: the deflationary tax->buyback->burn design + trust properties (renounced, LP burned, fair launch). Describes how the token works, NOT a buy recommendation.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds meaningful framing beyond that: it is 'neutral, verifiable,' informational, and explicitly not an endorsement. It also reveals the kind of content the tool returns by listing tax->buyback->burn, renounced contract, burned LP, and fair launch. No contradiction with annotations is present.
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 with no filler. The first sentence leads with the core purpose and concrete token mechanics, and the second sentence adds a valuable boundary ('NOT a buy recommendation'). Every clause earns its place.
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?
For a parameterless, read-only informational tool, the description is complete: it states what is covered, the key topics, and an important disclaimer. There is no output schema, but 'describes how the token works' sufficiently tells an agent what kind of response to expect.
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 is empty with zero parameters, so there are no parameter semantics to document. The description still compensates by explaining the subject matter and scope, which is sufficient for a parameterless informational tool.
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 names a specific resource ($BOBAI) and a specific function: describing the token's neutral, verifiable value-accrual mechanics. It details the exact scope — deflationary tax->buyback->burn design and trust properties — and explicitly says it 'describes how the token works,' not a buy recommendation. This clearly differentiates it from siblings like bobai_price or bobai_purchase_guide.
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 clear context for when to use the tool: when an agent needs the token's mechanics, design, and trust properties rather than a price or a recommendation. It explicitly states what it is NOT (a buy recommendation), which is a useful exclusion. However, it does not name alternative sibling tools or give explicit when-to-use vs. when-not-to-use conditions, so it stops short of full routing guidance.
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 operate on overlapping data: bobai_burned, bobai_activity, and bobai_smart_money all report burn-related metrics, while bobai_token_info, bobai_circulating_supply, and bobai_burned overlap on supply numbers. The long descriptions mitigate this, but the purpose boundaries are less crisp than ideal. The BSC pool tools are more easily told apart.
Most token tools use a consistent bobai_* snake_case prefix, but the set mixes conventions: bnb_agent_*, bsc_pool_scan, find_agents_on_bnb_chain, and pancakeswap_fee_tiers break the pattern. The names are still readable and mostly noun-oriented. There is no chaotic mixing of camelCase or vague verbs, but the pattern is not uniform.
19 tools sits in the borderline heavy range for a token research server. Many are focused data views, but some could be consolidated, such as bobai_token_info with circulating supply/burned, or the informational guide/links/tokenomics cluster. Each tool has a defensible role, but the overall surface feels padded.
Core workflows are well covered: price, liquidity, DEX parameters, purchase guidance, burns, wallet balances, and BNB agent discovery. Missing historical price/volume, holder distributions, or detailed per-agent profiles, but these are minor gaps rather than dead ends. The server gives an agent what it needs to understand and interact with $BOBAI.