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

Beyond the readOnly and openWorld annotations, it discloses that data may be up to 15 minutes old, that this is a free sample, and that the JSON shape matches the paid /v1/pulse endpoint. These are exactly the behavioral traits an agent needs to decide whether freshness matters.

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 front-loaded with the free-sample purpose, then lists contents, staleness, and the alternative in a compact set of sentences. Every sentence earns its place.

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?

With no output schema and zero parameters, the description carries the burden of explaining return content, and it does so by enumerating the included data and noting the shared JSON shape with the paid endpoint. Staleness is also disclosed, making the definition complete for 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?

There are zero input parameters, so the baseline is 4 per the rubric. The schema is empty and requires no parameter explanation, but the description does not need to add parameter semantics.

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 this is a free crypto market pulse sample and enumerates its contents: spots, Fear & Greed, Hyperliquid funding, DefiLlama TVL/yields, and a plain-English summary. It explicitly contrasts with the paid sibling get_market_pulse, so an agent can distinguish it without inspecting schemas.

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 directly tells the agent to use get_market_pulse for live paid data, implicitly framing this tool as the free/stale-data alternative. The condition selecting the alternative is explicit, leaving little to inference.

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