netintel_market_snapshot

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

With no annotations, the description carries the full behavioral burden. It discloses that the four sections are 'fetched concurrently,' which is a genuine behavioral trait, and the data-only framing implies read-only operation. It says nothing about auth, rate limits, caching, or failure behavior per section.

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?

Purpose is front-loaded in a single efficient sentence and every clause carries content (the four sections). The fiat-pair enumeration is slightly over-detailed and the trailing ellipsis cuts off mid-thought, but overall it is dense and well-ordered.

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?

No output schema exists, so the description should carry return-shape context; enumerating the four sections partly does this. But it omits parameter meaning and any per-section structure, so for a multi-section aggregator with 0% param coverage it is only adequate.

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 0% for both 'vs' and 'symbols', so the description must compensate and does not — neither parameter is mentioned. The fixed lists (BTC/ETH/SOL, the fiat pairs) hint at defaults but leave it ambiguous whether those are overridable via the params.

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 composite resource and enumerates exactly what it bundles: BTC/ETH/SOL spot + 24h moves, fiat crosses, Base/Ethereum gas with USD cost, and fear/greed. That is concrete enough for an agent to know what it returns. It never differentiates itself from siblings that cover the same ground (netintel_crypto_market, netintel_gas_price, netintel_crypto_price), so it stops short of a 5.

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 'one-call' framing implies this is the aggregated alternative to hitting several narrower tools, which is useful implied guidance. However there is no explicit when-to-use/when-not statement and no naming of the overlapping siblings it should replace.

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