okx_get_stable_rewards_product

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

The label '[L:READ]' hints that this is a read operation, but no annotations are provided to confirm or elaborate. The description does not disclose any behavioral traits such as data freshness, authorization requirements, or side effects. With no annotations, the description carries the burden but offers 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 very short, consisting of a single line. While concise, it is under-specified and fails to convey the tool's purpose or behavior. Every sentence should earn its place, but this one omits critical information, making it more an instruction than a proper description.

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 complexity of the tool environment with many sibling tools, the description is completely inadequate. It does not explain what the tool returns, when to use it, or how it differs from similar tools like okx_get_stable_rewards_apy. The prerequisite is noted but without any context about the tool's functionality.

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 no parameters, so schema description coverage is 100%. The description adds no parameter information, but none is needed. A baseline score of 3 is appropriate because the schema already handles the param semantics fully.

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 does not state what the tool does; it only provides a category label and a prerequisite to call agent_catalog. The tool name 'get_stable_rewards_product' suggests a read operation, but the description fails to clarify the specific resource or action. This is a tautology of the name at best, and at worst, it omits the core 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 includes a directive to call agent_catalog first, which is a prerequisite for using the tool. However, it provides no guidance on when to use this tool versus alternatives like okx_get_stable_rewards_apy or okx_get_stable_rewards_history. The context for selection is absent.

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