cn402_solar

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

No annotations are provided, so the description must cover behavioral traits. It correctly notes that it handles leap months and is a conversion function. However, it omits details about output format, error handling for invalid dates, or any required authentication. The price mention is irrelevant to tool behavior.

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 starts with the core purpose but then repeats equivalents in different languages and adds an irrelevant price line. It could be streamlined to a single clear sentence. The structure is adequate but not concise.

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 there is no output schema, the description should explain the return value format (e.g., a date string like '2026-01-15'). It does not. It also doesn't mention constraints like valid lunar year ranges or error behavior. The description is incomplete for safe agent usage.

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 coverage is 100%, so baseline is 3. The description adds little beyond the schema: it restates the valid ranges (day 1-30, month 1-12) and mentions the 'leap' parameter defaults to false, but these are already in the schema descriptions. No additional semantic value.

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?

Description explicitly states multiple phrasings for the conversion (lunar to solar, Gregorian, Western calendar) and uses specific verbs like 'Convert' and 'reverse lookup'. It clearly distinguishes from sibling tools like cn402_lunar which likely does the opposite conversion.

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?

While the description implies it is for lunar-to-solar conversion and mentions 'reverse lunar calendar lookup', it does not explicitly state when to use this tool versus alternatives like cn402_lunar (solar-to-lunar) or other calendar tools. No 'when not to use' guidance is provided.

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