ultrade_system_time

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get current system time,' which implies a read-only operation, but does not disclose any behavioral traits such as rate limits, authentication requirements, or what format the time is returned in. This leaves significant gaps for a tool with zero annotation coverage.

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 'Get current system time' is a single, efficient sentence that is front-loaded and wastes no words. It directly conveys the tool's purpose without unnecessary elaboration, making it highly concise and well-structured.

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 the tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally complete. It states what the tool does but lacks details on behavioral aspects like return format or potential errors. Without annotations or output schema, more context would be helpful, but it meets the basic requirement for a simple tool.

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 0 parameters with 100% coverage, so no parameter information is needed. The description does not add parameter semantics, but this is acceptable as there are no parameters. Baseline is 4 for 0 parameters, as the description does not need to compensate for any gaps.

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 'Get current system time' clearly states the verb ('Get') and resource ('current system time'), making the purpose specific and unambiguous. It effectively distinguishes this tool from its siblings, which are focused on market operations, wallet management, and other system functions like maintenance or version checks.

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 usage by stating 'Get current system time,' suggesting it should be used when the current system time is needed. However, it does not explicitly guide when to use this tool versus alternatives (e.g., other time-related tools if they existed) or provide exclusions. The context is clear but lacks explicit alternatives or when-not-to-use guidance.

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