get_solar_term

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

No annotations are provided, so the description bears full burden. It discloses the tool retrieves an exact date and gives an example (Lichun ~Feb 4). While it does not specify output format or error handling, the simplicity of the tool and presence of an output schema mitigate concerns.

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 brief and well-structured: a clear purpose sentence, an explanatory note about 24 terms, and concise parameter descriptions. Every sentence is informative and no words are wasted.

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 the tool's low complexity, the presence of an output schema (which covers return values), and distinct siblings, the description provides sufficient context. It answers what, how, and the range of inputs without missing essential details.

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?

With 0% schema description coverage, the description compensates fully by explaining both parameters: year is a year like 2026, term_number is the solar term index 1-24 with examples. This adds significant meaning beyond the raw integer types.

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 retrieves the exact date of a solar term for any year, using specific verbs and resource. It is distinct from siblings like get_daily_pillars or get_natal_chart, which cover different concepts.

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 explains the tool's scope (any year, term numbers 1-24) but does not explicitly state when to use it over alternatives. However, the sibling context makes the usage obvious, as other tools serve different purposes.

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