netintel_crypto_market

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses data sources (Coinbase Exchange, CoinGecko), quote currencies, and a truncated '60s…' hint about refresh/cache timing, but omits authentication needs, rate limits, error behavior, and the meaning of the '60s' interval. Partial behavioral context only.

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 dense sentence that front-loads the core purpose and data fields efficiently. However, the trailing '60s…' is truncated and incomplete, which slightly hurts structure and leaves a dangling detail.

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 and no annotations, the description does a good job listing the returned fields and their sources. It remains incomplete regarding parameter formats, usage routing, and the truncated '60s…' rate/cache behavior, but covers the essential return value landscape better than most.

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%, so the description must compensate. It explains the 'vs' parameter by listing USD, EUR, and GBP, and implies the 'symbol' parameter through '~50 top assets', but does not specify symbol format (e.g., BTC vs bitcoin) or whether 'vs' has a default. It adds partial meaning beyond the empty schema.

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 (live crypto market data for ~50 top assets) and explicitly lists the combined data fields (spot price, 24h OHLCV, change, market cap, rank, supply) and sources (Coinbase Exchange, CoinGecko). This distinguishes it from sibling tools like netintel_crypto_price or netintel_crypto_ohlc that provide narrower single-source data.

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 explicit when-to-use guidance, no when-not-to-use conditions, and does not name alternatives such as netintel_crypto_price or netintel_market_snapshot. Usage is only implied by the data content.

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