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

With no annotations, the description carries the full burden. It discloses the sign convention ('Positive rate = longs pay shorts'), which is a non-obvious behavioral detail, and clarifies the scope ('every tracked exchange/symbol pair'). It does not mention any limitations like rate limits or pagination, but given it is a simple read-only tool with no parameters, the disclosed behavior is adequate.

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 no fluff. The primary purpose is stated first, and the second sentence adds a valuable clarification about the sign meaning. It is front-loaded and every word 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?

For a parameterless tool with an output schema, the description is complete. It states what data is returned and the scope, while the output schema presumably defines the response structure. Nothing needed to invoke the tool correctly is missing.

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 input schema is empty. The baseline for 0-parameter tools is 4, and the description adds no parameter details because there are none to document. It correctly focuses on output semantics instead.

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 retrieves latest perpetual funding rates and mark prices for every tracked exchange/symbol pair. The verb 'get' and resource are specific, and the 'latest' qualifier distinguishes it from historical tools like get_funding_history and get_funding_dispersion, even without naming them 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?

The description provides no guidance on when to use this tool versus alternatives such as get_funding_history for historical data or get_funding_dispersion for distribution analysis. It simply describes what it returns, leaving the agent to infer its appropriate context.

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