get_current_datetime

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

With no annotations, the description must convey behavior fully. It mentions SSH, indicating a remote operation, but fails to disclose whether a new connection is opened, potential side effects (e.g., host key acceptance), error handling, or the fact that it requires network access. This is insufficient for a tool with 7 parameters.

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 a single clear sentence, front-loaded with the essential information. No unnecessary words or 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?

Given the tool has 7 parameters and no schema descriptions, the description is too brief. It does not explain what the output (datetime) looks like despite an output schema existing, nor does it cover parameter details or prerequisites like SSH key setup. The 'via SSH' hint is insufficient for full contextual completeness.

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 schema description coverage is 0%, meaning the schema provides no parameter explanations. The description does not add any parameter semantics, ignoring all 7 parameters (host, user, port, password, key_path, timeout, accept_new_hostkey). This is a critical omission.

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 clearly states the tool collects current datetime from a remote Linux host via SSH. The verb 'collects' and resource 'current datetime' are specific, and it distinguishes itself from sibling tools like get_disk_free or get_memory_pressure which focus on other system metrics.

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 for retrieving datetime over SSH but does not provide explicit guidance on when to use this tool vs alternatives, such as checking if SSH is available or comparing with other remote data tools. No when-not-to-use conditions are mentioned.

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