getContracts

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

Declares read-only and describes error conditions. No annotations provided, so description carries full burden. Could mention if pagination or rate limits apply, but overall clear.

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?

Description is thorough yet well-structured, front-loading the main purpose. Each sentence provides useful information. Slightly long but justified given the content.

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?

Fully covers usage, prerequisites, alternatives, param details, and edge cases. No output schema exists, but description doesn't need to explain return values as it's a list of contracts.

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%, but description adds useful context: examples of platformId values, explanation of limit's purpose and cap, and behavior on unknown platformId. Adds value beyond 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?

Clearly states the tool lists token contract addresses for a platform, mapping to CoinPaprika coin ids. Provides specific use cases and distinguishes from sibling tools like getTickerByContract and getHistoricalTickerByContract.

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?

Explicitly instructs to find platformId first via getPlatforms and directs users to alternative tools for single contract price or history. Also explains param behavior and error on unknown platformId.

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