okx_reset_rfq_mmp

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the operation is destructive, what permissions are needed, or side effects. The '[L:READ]' hint is ambiguous for a reset action.

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, but it could be improved by using clearer language instead of cryptic symbols. It prioritizes compactness over clarity.

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?

For a tool named 'reset_rfq_mmp', the description is too sparse. It does not explain the tool's behavior, return values, or relationship to other tools. Given the lack of output schema and annotations, this is insufficient.

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 tool has zero parameters and schema coverage is 100%, so the schema leaves no room for additional meaning. However, the description does not add any context about what the tool resets or how it works, which would be helpful.

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 'reset_rfq_mmp' does. It only includes a category label and a hint to call agent_catalog first. The purpose is vague and requires inference from the tool name and sibling tools.

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 tells the user to call agent_catalog first, but does not provide any context on when to use this tool versus alternatives like okx_reset_mmp or okx_set_mmp_config. No exclusions or comparison are given.

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