get_today_date

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

No annotations are provided, so the description carries the burden. It states it returns the current date and lists formats, but does not explicitly disclose read-only nature, timezone behavior, or any system dependency. However, the operation is inherently non-destructive and the description is not misleading.

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 with the main verb and resource. The format list is necessary and concisely presented with inline examples, earning its place 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?

For a simple tool with one optional parameter and no output schema, the description covers all necessary information: the purpose, the parameter's allowed values, and their meaning. No additional context is required.

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 provides the enum values, but the description adds significant meaning by mapping each enum to its exact date pattern (e.g., 'european (DD.MM.YYYY)', 'iso (YYYY-MM-DD)'). This goes beyond the schema's minimal description 'Datumsformat'.

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 tool's function: 'Gibt das aktuelle Datum zurück' (returns the current date). It lists all supported formats, which provides specific and unambiguous resource scope.

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 the usage context: use this tool whenever you need the current date. There are no sibling tools or alternatives, so it cannot provide exclusions or comparisons, but the context is clear.

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