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

With no annotations, the description carries the full burden. It transparently discloses that no payment is required and that the output is a 'small live subset', conveying the key behavioral trait of being a free, limited sample. It doesn't note data latency or exact limitations beyond 'small', but that's acceptable for a sample.

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 sentence that front-loads the key fact ('FREE sample'), then lists the contents efficiently. Every word contributes value, with no extraneous detail.

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 tool with no output schema, the description adequately states what is returned (prices + Base chain snapshot). It doesn't specify the structure of the snapshot, but given the tool's simplicity, this is a minor gap rather than a major omission.

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, and the schema is empty, so the description doesn't need to explain any. Baseline for 0 params is 4, and the description adds no parameter-related information, which is appropriate.

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 returns a free sample of the paid crypto market pulse output, listing specific assets (BTC/ETH/SOL/USDC) and a Base chain snapshot. It distinguishes itself from the sibling crypto_market_pulse by explicitly labeling itself as the free sample version.

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?

It explicitly says 'FREE sample' and 'no payment required', indicating it is the no-cost alternative to the paid crypto_market_pulse. However, it doesn't explicitly exclude other sibling tools like usdc_on_base_stats or mention when not to use it, so some inference is needed.

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