okx_get_public_block_trades

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

No annotations are provided, so the description must carry full burden. It indicates a read operation via [L:READ] but does not disclose other behavioral traits such as permissions, rate limits, or side effects. The instruction to call agent_catalog implies a prerequisite but is not explained.

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 short, but its cryptic format and non-standard prefixes reduce clarity. It is not well-structured for an AI agent to parse and understand the tool's purpose.

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?

No output schema is provided, and the description does not explain the tool's return value or behavior. The prerequisite to call agent_catalog is mentioned but not justified, leaving the context incomplete.

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 one parameter (instId) described in Chinese. The description adds no additional meaning beyond the schema, so it meets the baseline for high coverage.

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 cryptic prefixes ([L:READ] CAT:[公共]) and a Chinese instruction to call agent_catalog, but does not explicitly state what the tool does. The name suggests getting public block trades, but the description does not confirm this, leaving the purpose unclear.

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 only guidance is to call agent_catalog first, but it does not explain when to use this tool versus alternatives. With many sibling trade-related tools (e.g., okx_get_trades, okx_get_block_ticker), no differentiation is provided.

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