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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly states that the tool returns a list of supported blockchains with specific fields and a minimum count, which is sufficient for a simple zero-parameter read operation. It does not mention rate limits or data freshness, but those are not critical for this straightforward listing tool.

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 front-loaded sentence that states the action, the scope, and the output fields with no wasted words. It earns its place entirely and is easy to parse quickly.

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 zero-parameter list operation with no output schema and no annotations, the description is fully sufficient. It explains what the tool returns and the scope of the blockchain list, leaving no major gap for an agent to call this tool correctly.

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 input schema has zero parameters, so there are no parameter semantics to clarify. The baseline of 4 applies here because the description correctly indicates this is a no-input listing operation without needing to add parameter details.

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 uses a specific verb (List) and names the exact resource (the 34+ blockchains CryptoPulse tracks) and the fields returned (id, name, symbol, category). It is clearly distinguishable from the sibling data tools like get_market_overview or get_whale_movements, which suggest operational data retrieval rather than a static chain list.

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 implies this is a reference/catalog tool, likely useful before querying chain-specific data from sibling tools, but it does not explicitly say when to use it or when not to use alternatives. No exclusionary guidance or direct comparison to sibling tools is provided, so the usage context is only implied.

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