cmc_altcoin_season_historical

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 implies read-only via 'Get' but does not explicitly state read-only behavior, side effects, auth requirements, rate limits, or response characteristics beyond what the output schema provides.

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?

A single front-loaded sentence with no filler; it states the resource and scope immediately.

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 simple historical-data retrieval with an output schema and an enum-constrained parameter, the description is minimally adequate. It omits selection guidance against the 'latest' sibling and does not elaborate on parameter values, but the structured fields cover enough for correct invocation.

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 the single timeframe parameter. The description mentions 'one provider-supported timeframe' but does not list the allowed values ('7d', '30d', '90d') or the default, leaving the schema's enum as the only source of parameter meaning.

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?

States a specific verb ('Get') and resource ('CoinMarketCap Altcoin Season Index history'), and the 'historical' scope distinguishes it from the sibling cmc_altcoin_season_latest. However it does not explicitly name an alternative or state exclusions, so it falls short of the top mark.

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 when-to-use guidance or alternative tools are named. The phrase 'for one provider-supported timeframe' is a parameter constraint, not usage context, so an agent must infer that this is for historical as opposed to latest data.

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