get_zodiac_info

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

With no annotations provided, the description carries the full burden of disclosing behavior. It describes the output comprehensively (animal, element, traits, etc.) and mentions yearly/daily info based on heavenly stems. It does not cover edge cases or other cultures, but for the primary Chinese zodiac case, it is transparent.

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 concise, with a clear front-loaded first sentence summarizing the purpose. Every sentence adds value: the second sentence enumerates output components, and the third specifies the system used. No unnecessary words.

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 description is fairly complete for Chinese zodiac, but it lacks explanation for other culture values and does not differentiate from overlapping sibling tools like get_daily_fortune or calculate_bazi. Without an output schema, the description should cover the return format for all cases, which it does not.

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%, so baseline is 3. The description adds value beyond the schema by detailing what is returned for the 'chinese' culture, including the list of 12 animals and five elements. However, it does not explain the 'culture' parameter for other possible values, which is a minor gap.

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 comprehensive zodiac information for a specific date, explicitly listing the components for Chinese zodiac. The verb 'retrieves' and resource 'zodiac information' are specific, and the detail distinguishes it from sibling tools that focus on compatibility, auspicious dates, etc.

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 provides clear context: use this tool when you need zodiac info for a date, especially Chinese zodiac. It does not explicitly mention alternatives or when not to use, but the context is clear enough for an agent to infer the primary use case.

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