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

The readOnlyHint and openWorldHint=false annotations already establish that this is a safe, closed-world read. The description adds useful domain context, notably that changes are measured from 00:00 UTC and that a "positioning flip level" is included, but it says nothing about data freshness, refresh cadence, ordering, or units.

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?

A single tight sentence with the scope front-loaded and the returned fields listed in a compact sequence. No filler, no repetition of the title, and nothing that could be cut without losing information.

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 input parameters and no output schema, the description must carry the return-value burden, and it does so by naming the five columns an agent will receive. It is slightly short of complete because it omits result ordering, units, and any sense of how many markets are returned.

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 takes zero parameters, so there is no parameter meaning to convey and the schema already fully covers the empty input. The baseline of 4 applies; the description cannot add value on this dimension.

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 concrete scope ("Every Swiftedge market in one table") and enumerates the exact data columns returned: live price, change since 00:00 UTC, funding rate, 24-hour open interest change, and positioning flip level. This clearly distinguishes the broad overview from siblings like get_market_snapshot or list_markets, though it never names those alternatives explicitly.

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?

Usage is only implied: an agent can infer this is the aggregate first-look tool versus per-market siblings from the word "overview" and "every ... market in one table." There is no explicit when-to-use statement, no mention of when to prefer get_market_snapshot or get_funding_and_open_interest instead, and no stated prerequisites.

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