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

With no annotations provided, the description carries the full behavioral burden. It states the fixed scope ('17 blockchains') and the returned fields, and 'List' implicitly conveys a read-only, non-destructive operation. It doesn't add extraneous behavioral detail, but it is sufficient for such a simple no-parameter 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 with zero filler. It packs the action, scope, exact count, and field list into minimal words, earning every character.

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 parameterless listing tool with no output schema, the description is complete: it tells the agent exactly what will be returned and which fields to expect. There are no hidden inputs, side effects, or return-format gaps that would prevent 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?

The tool has zero parameters, so the baseline of 4 applies. There are no parameter semantics for the description to clarify, and the schema already fully declares that no input is required.

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 resource ('17 blockchains CryptoPulse tracks') and enumerates the exact fields returned (id, name, symbol, category). This clearly distinguishes it from the sibling get_* tools, each of which targets a different kind of data.

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 clearly implies when to use the tool: whenever the agent needs the list of blockchains CryptoPulse tracks, with no ambiguity about purpose. It doesn't explicitly mention alternatives or exclusions, but none are needed given the tool's distinct list-only role among the siblings.

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