okx_get_prompts

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

Without annotations, the description carries the burden of conveying safety and behavior. The word 'View' strongly implies a non-mutating, read-only operation. It also discloses that it returns both default and custom prompts, adding useful behavioral context beyond the schema.

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 concise at two sentences, with no wasted words. Information is front-loaded: the main action and target are in the first sentence, and an important detail (default vs custom) is in the second.

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 tool is simple with one optional parameter and no output schema. The description clearly conveys what the tool does and the scope (all 4 agents). It omits the output format (e.g., plain text, JSON), but given the simplicity and clarity of the action, this is a minor gap rather than a significant deficiency.

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% parameter description coverage, including the 'agentId' parameter with enum values and a description. The tool description does not add any details about the parameter, so it provides no extra value beyond the schema, justifying the baseline score 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 uses a specific verb ('View') and a clear resource ('current system prompts for all 4 AI agents'), and further specifies that it shows both default and custom prompts. This clearly distinguishes it from sibling tools like okx_update_prompt, which performs a different action.

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 implies when to use this tool (when you want to view prompts) and the read-only nature is clear. It does not explicitly mention alternatives or exclusions, but no competing tool exists for reading prompts, so the context is sufficiently clear.

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