get-current-date

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

The description fully discloses the timezone (Asia/Shanghai, UTC+8), date format (yyyy-MM-dd), and primary use case. With no annotations provided, the description effectively conveys all necessary behavioral traits for a read-only, deterministic tool.

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 extremely concise—two sentences that immediately state the purpose, timezone, format, and use case. Every sentence adds value 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?

Given the tool's simplicity (no parameters, no output schema), the description covers all relevant context: timezone, format, and intended usage. Nothing is missing for an agent to correctly invoke the 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 zero parameters, so the input schema is complete. The description adds no parameter-specific info, which is acceptable as there are none. Baseline 4 is appropriate.

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 explicitly states the tool's function: get current date in Shanghai timezone with a specific format. It also explains its utility in parsing relative dates, making the purpose very clear.

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 provides a specific usage context (parsing relative dates like 'tomorrow', 'next Wednesday'), guiding when to use this tool. While no explicit alternatives or exclusions are given, the simplicity of the tool makes this sufficient.

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