Tradfi Markets

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

Beyond the readOnlyHint annotation, the description discloses that the correlation is computed locally from klines with at most two klines calls, caching when possible, and an honest note when data is insufficient. This gives useful operational context without contradicting the annotations.

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 main functionality is front-loaded and every sentence contributes: core map, correlation sub-block, window semantics, and an example. It is dense with parenthetical lists but not bloated given the complexity.

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 read-only screener with an output schema, the description covers the main behavior, window choices, and a call example. It lacks explicit when-to-use guidance and limit semantics, but is largely complete for 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?

With 0% schema description coverage, the description must carry parameter documentation. It documents window with valid values and purpose, but says nothing about the meaning or behavior of limit beyond the example call, leaving a real gap.

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?

States it is a TradFi-perp screener that produces a local asset-class map by baseAsset with per-class volumes/prices/funding, plus a correlation sub-block. This identifies the resource and operation clearly and distinguishes it from generic siblings like market_overview or spot_overview.

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 implies usage through its screener framing and window parameter, and provides an example call. However, it never explicitly explains when to choose this tool over its siblings or when not to use it.

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