get_current_datetime

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

The description lacks behavioral details such as the return format (string, object), timezone handling, or any side effects. With no annotations, the description carries full burden but only offers a basic statement, missing key traits like output structure.

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 sentence, front-loaded, and contains no superfluous words. It is highly concise and directly states the tool's purpose.

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 absence of an output schema, the description should hint at the return value (e.g., format, timezone). It does not, leaving the agent guessing. The tool is simple but still incomplete for practical use.

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 covers the 'timezone' parameter (100% coverage), so the description adds no extra value. Baseline 3 is appropriate as the schema already does the job.

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 states the verb 'Get' and the resource 'current date and time', clearly indicating the function. However, it does not differentiate from the sibling tool 'get_current_date', which is similar but for date only. The name itself includes 'datetime', but the description misses the opportunity to clarify the distinction.

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?

No guidance is provided on when to use this tool over the sibling 'get_current_date'. There are no context cues or mentions of alternative tools, leaving the agent without decision support for tool selection.

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