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

No annotations are provided, so the description carries the full burden. It does add the context that the conversion uses the Vietnamese calendar, which is a useful behavioral detail. However, it does not disclose potential edge cases (e.g., invalid dates, timezone dependence) or explicitly state that it is a pure calculation with no 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, clearly front-loaded sentence that states the tool's purpose without any fluff or repetition. It earns its place with essential information only.

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 is simple with one parameter and no output schema. The description adequately covers the core purpose and the calendar system. It does not specify the return format, but the output is logically inferable from the tool name and description, making it reasonably complete for a low-complexity 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 input schema covers 100% of the parameter, including format and an example. The description adds no additional semantic detail beyond what the schema already provides, so the baseline of 3 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 clearly states the tool converts a solar date to a lunar date, specifying the calendars (Gregorian to Vietnamese). The verb 'convert' is specific, and the direction is explicit, distinguishing it from the sibling tool convert_date_lunar2solar.

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?

Usage is implied by the description: if you have a solar date and need a Vietnamese lunar date, use this. However, it does not explicitly state when to prefer this over alternatives, nor does it mention the inverse tool or any exclusions. The guidance is minimal.

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