getHistoricalTickerByContract

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

No annotations are provided, so the description carries full burden. It discloses read-only nature, subscription requirement (Starter+ plan from COINPAPRIKA_API_KEY), and parameter defaults/constraints. However, it does not describe the return format or pagination behavior, which would be helpful given no output schema.

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 dense but well-structured: main purpose first, then use cases, then parameter details. It is slightly verbose but every sentence adds value. Could be tightened but still effective.

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?

Given 7 parameters (3 required), no output schema, and 28 sibling tools, this description is remarkably complete. It covers all parameters with defaults, constraints, and examples, mentions auth requirements, and provides usage context. No gaps for a historical data retrieval tool.

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 coverage is 100%, and the description adds significant value beyond schema: clarifies start as required, end as optional defaulting to now, interval default '5m', quote default 'usd', limit default 50 with max 250, and explains platformId and contractAddress with examples.

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 it retrieves historical price and market history by contract address as a time series. It distinguishes from siblings like getTickerByContract (current price) and getTickersHistoricalById (by coin id), making the purpose unambiguous.

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?

Provides explicit use cases ('Use for 'token price on 2024-01-01 by address', 'hourly history for a contract'') and directs to alternatives for current price or by coin ID, offering clear when-to-use guidance.

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