okx_get_announcements

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

No annotations are provided, so the description must convey behavioral traits. It adds '[L:READ]' for read-only hint but lacks details on authentication, rate limits, or response format. The tag format is non-standard and incomplete.

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 terse (one line with tags) but lacks a clear sentence structure. It sacrifices clarity for brevity, making it hard to parse.

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 simple parameters, the description should clearly state the tool's core function. It fails to do so, relying on the name and cryptic tags. The reference to 'agent_catalog' is unexplained.

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?

Parameter schema coverage is 100%—both 'lang' and 'annType' have descriptions. The description adds no extra parameter semantics beyond the schema, earning the baseline score.

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 cryptic tag format ('[L:READ] CAT:[公共] | → 请先调用 agent_catalog') instead of a clear statement. The tool's purpose is implied by its name and parameters, but the description does not explicitly say 'get announcements from OKX'.

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 hints at a prerequisite ('call agent_catalog first') but provides no guidance on when to use this tool over alternatives. No explicit when/when-not or sibling comparisons are given.

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