market_time

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

没有注解，描述承担所有行为说明责任。它说明返回时间信息，但未透露是否只读、限速等特质。对于时间工具，基本行为透明但不够详尽。

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?

一句话描述，简洁且重点突出，没有冗余信息。

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?

对于无参数、无输出schema的工具，描述涵盖了目的和返回值，但未详细说明返回格式。大体完整，可补充字段结构。

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?

无参数，schema覆盖100%，描述在schema基础上增加返回值含义（本地时间、偏差），符合基线4。

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?

描述明确指出获取期货服务器时间（Unix毫秒），并返回本地时间和偏差用于校准。动词'获取'和资源'服务器时间'清晰，且与其他工具区分度高。

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?

描述暗示用于获取服务器时间并进行时钟校准，但没有明确说明何时不使用或备选工具。由于没有其他工具提供相同功能，使用场景较清晰。

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