crypto-pulse

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

No annotations are provided, but the description discloses the data sources (DRPC + CoinGecko), the cost ($0.007/call), and the output fields. This is sufficient for a read-only data tool. It does not mention any destructive or side effects, which is appropriate.

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 paragraph that packs in a clear statement of purpose, return fields, use cases, data sources, and cost. It is well-structured and front-loaded, though could be slightly more concise.

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 the tool has no output schema, the description details the return fields comprehensively. It explains the data sources and use cases. It does not cover error conditions or rate limits, but for a simple data retrieval tool with two optional parameters, it is adequately complete.

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?

The schema coverage is 100%, and the description adds meaning beyond the schema: it specifies that 'network' can be 'ethereum' or 'Base' (schema only says 'Chain for block context' and default 'ethereum'), and that 'movers_limit' ranges from 1-20 (schema only says '1–20'). This provides valuable context for parameter usage.

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 the tool provides 'Crypto market pulse — latest Ethereum (or Base) block context plus top crypto gainers and losers by 24h change, in a single call.' It lists the specific data fields returned and distinguishes itself from siblings like 'crypto-top-movers' and 'eth-block' by combining both in one call.

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 explicitly suggests use cases: 'Use for crypto portfolio context, on-chain/market correlation, or pre-trade situational awareness.' It also mentions cost savings compared to a two-endpoint chain. However, it does not mention when not to use or specific alternatives.

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