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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered elsewhere. The description earns credit by adding the sign convention ('Positive rate = longs pay shorts'), which is interpretive context an agent needs to reason about the values and which no structured field provides.

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?

Two short sentences, both load-bearing: the first defines the payload and scope, the second defines how to read the numbers. Nothing is repeated from the schema or annotations and the scope statement is front-loaded.

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 no-parameter, read-only snapshot tool with an output schema already defined, the description covers what is returned and how to interpret it. The only remaining gap is freshness or refresh cadence, which an agent might want given 'Latest' is doing a lot of work.

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 semantics to explain and the baseline of 4 applies. The description correctly implies no filtering is possible by framing the result as covering every tracked exchange/symbol pair.

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 names a specific verb-resource pair ('Latest perpetual funding rates and mark prices') and the scope ('every tracked exchange/symbol pair'), so the agent knows exactly what data comes back. It stops short of naming the sibling it differs from, which matters here because get_funding_history, get_funding_arbitrage, and get_funding_dispersion all sit adjacent.

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?

'Latest' implies a current snapshot rather than a time series, which implicitly routes the agent away from get_funding_history. However, there is no explicit when-to-use statement and no mention of when get_funding_arbitrage or get_funding_dispersion would be the better pick.

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