okx_smart_trader_detail

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

With no annotations, the description bears full burden for behavioral disclosure. It indicates read-only via '[L:READ]', but lacks details on behavioral traits such as rate limits, authentication needs, or side effects. The description provides minimal transparency.

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 brief but under-specified. It is not efficiently meaningful; conciseness should not sacrifice clarity. The single line provides insufficient information, earning a low score.

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 no output schema and the tool's likely complexity (detailed trader info), the description fails to convey return structure or behavior. The prerequisite to call agent_catalog is vague. Overall incomplete for effective use.

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 description coverage is 100%, with clear parameter types and descriptions in the schema. The description adds no additional semantic value beyond the schema, meeting the baseline of 3.

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 cryptic ('[L:READ] CAT:[Smart Money]') and does not explicitly state what the tool does. It implies reading details of a smart trader but fails to articulate the core function, making it unclear for an agent to understand the tool's purpose.

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 advises to call agent_catalog first, providing some prerequisite context, but no guidance on when to use this tool versus alternatives like okx_smart_leaderboard. Without explicit usage scenarios, the agent may misuse the tool.

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