date

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

Description claims 'parse a supplied date string' but input schema has no string parameter, which is misleading. Annotations provide readOnlyHint=true and description adds no side effects, but functionality discrepancy lowers score.

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?

Concise, front-loaded with primary purpose, uses efficient multi-sentence format without 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?

Explains output format (JSON with ISO 8601, timezone-aware) and main uses, but does not clarify the lack of a parse string parameter. No output schema present, but description partially compensates.

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?

Schema coverage is 100% with descriptions for all 5 parameters. Description provides overall context but no additional detail per parameter beyond 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 clearly states 'Return current system time or parse a supplied date string as structured JSON' with a specific verb and resource. It distinguishes from sibling 'uptime' by mentioning not for elapsed time.

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?

Explicitly says when to use (query system clock, validate date strings) and when not to (not for measuring elapsed time, use 'uptime' instead). Names alternative 'uptime'.

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