okx_smart_leaderboard

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

No annotations are provided. The description only contains '[L:READ]' which hints at read-only nature but does not explain it. No disclosure of side effects, authentication needs, rate limits, or other behavioral traits. The burden is on the description, and it fails.

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 very short (one line) but lacks critical information. Conciseness is achieved at the expense of utility. Important details are missing, making it not effectively 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?

The description does not explain what the tool returns (no output schema). It mentions a dependency on agent_catalog but does not describe the data or behavior. For a tool with three parameters and no output schema, this is grossly 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?

The input schema has 100% description coverage for its three parameters, so the baseline is 3. The tool description does not add further meaning to the parameters, but the schema already explains them adequately.

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 is vague. It includes 'CAT:[Smart Money]' and a prerequisite note, but does not explicitly state what the tool does (e.g., retrieves smart money leaderboard data). The name 'smart_leaderboard' implies the purpose but the description adds no clarity.

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 a prerequisite ('call agent_catalog first') but no guidance on when to use this tool over siblings like okx_smart_trader_detail or okx_smart_sentiment. No exclusions or alternatives are mentioned.

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