get_datetime

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states that the operation returns the current local date, time, and timezone, which is a read-only operation. It doesn't mention any side effects, but for a simple getter there are none. The description adequately conveys the expected 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?

A single, direct sentence with no filler. The core purpose is front-loaded and every word adds value. It is the ideal level of conciseness for a parameterless getter.

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 no parameters, an output schema exists (so return format is handled there), and the operation is straightforward, the description is complete. An agent has everything needed to invoke this tool correctly without additional context.

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 tool has zero parameters, so the description doesn't need to explain parameter usage. The baseline for a no-parameter tool is 4, and the description adds nothing beyond the schema, but there's nothing to add. The description is consistent with the empty schema.

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 a specific verb ('Get'), a specific resource ('WLAN Pi's current local date, time, and timezone'), and clearly enumerates the returned fields. It distinguishes itself from the sibling get_timezone by including date and time, so an agent can tell them apart without inspecting schemas.

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 clearly implies when to use it (when you need the full local date/time/timezone combination) but does not explicitly mention alternatives or when not to use it. Given the sibling get_timezone exists, explicit exclusion would be helpful, but the context is still clear enough for correct selection.

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