get_time_info

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

The description states it gets current time and last trading day, but lacks detail on whether the time is real-time or cached, timezone, or the format of the timestamp. With no annotations, more specificity would improve transparency.

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?

A single sentence that conveys all necessary information without redundancy. Every word adds value.

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?

For a tool with no parameters and no output schema, the description adequately covers what the tool returns. However, it could be more complete by specifying timezone or timestamp unit.

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?

With zero parameters, the schema provides no semantics. The description adds meaning by outlining the outputs (ISO format, timestamp, last trading day), fulfilling the baseline expectation.

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 specifies the exact outputs (ISO format, timestamp, last trading day) with a clear verb ('Get') and resource ('current time'). It clearly distinguishes from sibling tools which are all financial data retrieval tools.

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?

While no explicit when-to-use guidance is given, the tool's purpose is self-evident and distinct from siblings. The description implies its use for obtaining time-related information without needing context from other tools.

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