DateTime-LocalMCPServer

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

With no annotations provided, the description carries full burden. It discloses the return format and structure (dictionary with status and datetime fields), which is valuable behavioral information. However, it doesn't mention potential limitations like system time accuracy, timezone handling beyond 'local', or execution characteristics (e.g., performance, side effects).

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 perfectly front-loaded with the core purpose in the first sentence, followed by a clear Returns section. Every sentence earns its place: the first defines what the tool does, the second explains the output structure. No redundant or verbose language.

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 simplicity (0 parameters, no annotations, but with output schema), the description is complete. It explains what the tool returns, the format, and the response structure. The output schema existence means the description doesn't need to exhaustively document return values, and it provides exactly what's needed for this straightforward utility 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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the absence of inputs. The description appropriately doesn't waste space discussing parameters, maintaining focus on the tool's purpose and output. This meets the baseline expectation for parameterless tools.

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 specific action ('Return') and resource ('current or today's local date and time'), with precise format specification ('ISO 8601'). It effectively distinguishes this tool from siblings like 'formatted_datetime' or 'timezone_datetime' by emphasizing local time without formatting options.

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 context by specifying 'local date and time' and 'ISO 8601 format', which helps differentiate it from siblings like 'unix_timestamp' or 'formatted_datetime'. However, it doesn't explicitly state when to choose this tool over alternatives like 'current_date' or 'current_time', missing explicit when/when-not guidance.

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