okx_get_mmp_config

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions a read permission tag '[L:READ]' and a category, but does not describe any behavioral traits such as authentication requirements, rate limits, or whether the tool is safe/idempotent. No side effects are disclosed.

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 fails to be clear. It front-loads a prerequisite instruction instead of the tool's purpose. While brevity is good, omitting essential information makes it inadequate.

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 is completely inadequate for a tool with no input schema, no output schema, and no annotations. It does not explain what MMP config is, what data the tool returns, or any expected behavior. An agent cannot understand the tool's role from this description.

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, so the description does not need to add parameter information. The baseline for zero parameters is 4, and there is no deduction since the description does not mislead about parameters.

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 fails to state what the tool does. It only provides a prerequisite instruction ('→ 请先调用 agent_catalog') and a category tag. The tool's name suggests it retrieves MMP config, but the description does not confirm this, leaving ambiguity.

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?

No contextual guidance is given for when to use this tool versus alternatives like okx_set_mmp_config or okx_reset_mmp. The description only instructs to call agent_catalog first, without explaining why or what conditions warrant using this tool.

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