botindex_stablecoin_flows

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions monitoring with labels but doesn't disclose critical traits like whether this is a read-only query, rate limits, authentication needs, data freshness, or what 'whale/exchange/bridge flow labels' entail operationally.

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 efficiently structured in a single sentence that front-loads key information (monitoring function, assets, chains, labels). The '$0.02' note is slightly cryptic but doesn't significantly detract from overall conciseness.

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 monitoring tool with no annotations and no output schema, the description is incomplete. It lacks details on return format, pagination, error handling, and behavioral constraints, leaving significant gaps for an AI agent to understand how to effectively invoke and interpret results.

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 100%, so the schema already documents all three parameters thoroughly. The description adds no additional meaning about parameters beyond implying monitoring scope, meeting the baseline for adequate but unenhanced parameter semantics.

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 monitors large stablecoin transfers (USDC/USDT) on Base and Ethereum with flow labels, which is a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'botindex_hl_whale_alerts' that might have overlapping functionality, preventing a perfect score.

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 no guidance on when to use this tool versus alternatives. It mentions '$0.02' which might imply a cost, but doesn't clarify use cases, prerequisites, or exclusions compared to other botindex tools that handle whale alerts or crypto intel.

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