solar_to_lunar

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the basic function without mentioning any limitations, error handling, or side effects. For example, it does not specify valid date ranges or behavior for invalid dates, which is a significant gap for a conversion 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 a single, clear sentence that efficiently conveys the tool's purpose without any unnecessary words. Every word is essential, and the information is front-loaded.

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 conversion tool with a well-defined schema and an existing output schema, the description is minimal but sufficient. However, it does not address potential caveats like date range constraints or error conditions, which a complete guide might include. Contextually adequate but not thorough.

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 description coverage is 100%, but the tool description adds no extra meaning to the parameters beyond the schema field descriptions (e.g., year, month, day). Baseline 3 is appropriate as the schema already documents the parameters adequately.

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 'Input a solar date and returns a lunar date' clearly states the tool's function using a specific verb ('converts') and resource ('solar date to lunar date'). It effectively distinguishes the tool from its sibling 'lunar_to_solar', which performs the reverse operation.

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 usage: when a conversion from solar to lunar calendar is needed. Although it does not explicitly state when not to use it or mention alternatives, the sibling tool 'lunar_to_solar' is the only other date conversion tool, making the use case clear. Lacks explicit guidance but adequate for the task.

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