bobai_smart_money

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It discloses that the data is verifiable and requires no API key, but does not discuss rate limits, idempotency, or whether data is cached. For a read-only signal tool, this is adequate but not thorough.

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 a single long sentence that packs many details. While all content is relevant, the lack of sentence breaks makes it harder to parse quickly.

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?

With no output schema, the description must explain return values. It covers multiple data categories (tax reserve, whale flows, buys, burn momentum) adequately. However, it does not mention time range flexibility or whether data is live vs. aggregated.

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?

There are zero parameters (schema coverage 100% via empty schema). Baseline is 4, and the description adds context about the data returned, which is sufficient.

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 specifically states 'Live smart-money signals for $BOBAI' and enumerates distinct data components (tax reserve, whale flows, recent buys ledger, burn momentum), clearly differentiating from sibling tools like bobai_price or bobai_token_info.

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 explicit guidance on when to use this tool versus the 13 sibling tools. The description implies it is for 'smart-money' insights, but does not state when to prefer it over alternatives like bobai_activity or bobai_trade_info.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.