okx_get_block_ticker

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

With no annotations provided, the description carries full burden. It indicates read-only via [L:READ] but lacks details on behavioral traits such as authorization requirements, rate limits, data freshness, or what 'block ticker' implies. Minimal disclosure beyond the read hint.

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 extremely concise but at the expense of clarity. It uses cryptic notations without explanation and is not front-loaded with a plain-language purpose. The structure is poor for quick understanding.

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 simple schema (1 param, no output schema), the description is highly incomplete. It does not explain what a block ticker is, how it differs from a regular ticker, or what the output contains. Leaves the agent with insufficient context to use the tool effectively.

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 coverage is 100% with a clear description for the only parameter 'instId'. The tool description adds no extra semantic meaning beyond what the schema already provides, so baseline of 3 is appropriate.

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?

Description uses cryptic tags (READ, CAT) and states a prerequisite (call agent_catalog) but fails to clearly state that the tool retrieves block ticker data for an instrument. The verb and resource are implied by the name but not explicitly stated in the description, making it vague.

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?

Provides a prerequisite (call agent_catalog first) but no guidance on when to use this tool versus siblings like okx_get_ticker, okx_get_block_tickers, or other market data tools. Does not differentiate usage contexts.

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