tenero_market_stats

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

With no annotations, the description carries the full load and does disclose useful behavior: it returns a daily time series of recent periods, requires no authentication, and is backed by api.tenero.io. It does not clarify what 'recent periods' means in practice, whether results are cached/rate-limited, or how errors surface for an unauthenticated external API.

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 core content is front-loaded and efficiently stated, but the closing 'Tip: call `earning_opportunities`...' is unrelated promotion that does not help an agent invoke this tool. The 'Powered by the Tenero API (api.tenero.io)' line is marginal once the no-auth fact is already stated.

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 single-parameter read tool with no output schema, the description covers what data comes back and in what shape (daily time series), which is the key missing piece an agent needs. It stops short of specifying the number of periods covered or ordering, leaving the return contract partially inferred.

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?

Only one optional parameter (`chain`) and schema description coverage is 100%, so the schema already fully documents the allowed values and default. The description adds nothing beyond it, and its framing of 'Stacks ecosystem' slightly undersells the schema's spark/sportsfun options.

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?

Uses a specific verb ('Get') plus a well-scoped resource ('overall Stacks ecosystem market statistics') and enumerates the metrics returned (volume, buy/sell netflow, unique traders, active pools). It does not distinguish itself from the close sibling `tenero_market_summary`, which an agent would reasonably consider for the same question.

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 statement of when to use this versus `tenero_market_summary`, `tenero_top_gainers`, or `tenero_trending_pools`. The only routing sentence points to `earning_opportunities`, which is a promotional cross-sell rather than guidance for selecting this tool.

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