format_date

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

With no annotations, the description must communicate that this is a pure, non-destructive formatting operation. It does not state what the tool returns (a string), whether it respects timezone/locale defaults, or if there are any 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 a single concise sentence with no filler. It is front-loaded and appropriately sized for a simple utility, though it could include a few more specifics without becoming verbose.

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?

The tool has four parameters and no output schema, and the description is minimal. While the schema covers parameters well, the description fails to mention the return type or the meaning of the format options, leaving important gaps for the agent.

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 thoroughly describes all four parameters, including defaults and enums (100% coverage). The description adds no extra semantic detail beyond the schema, so it meets the baseline.

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 identifies the operation: formatting a date. However, 'various styles' is imprecise and relies on the schema for the actual format enum. It doesn't explicitly distinguish this tool from sibling date/time tools.

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?

No usage guidance is provided. There is no mention of when to prefer format_date over convert_time or get_current_time, nor any exclusions. The intended use is only implied by the verb.

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