pulse_market_overview

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

No annotations are provided, so the description must convey behavioral traits fully. It discloses the returned data fields and includes a calculation formula for funding APR. While it doesn't mention auth or rate limits, the tool is a simple read-only alias, and the description covers the key behavioral aspects adequately.

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 two sentences with zero waste. It front-loads the deprecation warning and then provides the payload details and usage guidance, making it efficient and easy to parse.

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's simplicity (a deprecated alias with two optional parameters, no output schema), the description is complete. It explains what the tool returns, provides a calculation hint, and references the preferred alternative. No additional information is needed for an agent to use 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?

Schema description coverage is 100%, so the baseline is 3. The description does not add new parameter details beyond what the schema already provides; it only reiterates the overall purpose. Thus, it meets the baseline but does not exceed it.

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 it is a deprecated alias for list_markets and lists the exact payload returned (24h volume, open interest, mark price, raw hourly fundingRate decimal, 24h change for every pair). It distinguishes itself from siblings by explicitly calling out the deprecation and directing users to list_markets for new integrations.

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 tells users to prefer list_markets for new integrations and indicates this tool is kept for backward compatibility only. This provides clear when-to-use and when-not-to-use guidance, along with the alternative tool name.

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