Kua Number

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

Annotations already indicate readOnlyHint, destructiveHint, and idempotentHint. The description adds context about the computation method (solar-year digit sum and gender) and the mapping to groups, which goes beyond annotations. No contradictions with annotations.

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 relatively short and front-loaded with the purpose. However, the inclusion of a nonexistent 'gender' parameter and lack of explanation for other schema parameters (latitude, longitude, timezoneOffset) detracts from conciseness and efficiency.

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?

With 4 parameters (date required, plus optional location fields) and no output schema, the description should explain the role of all parameters and the return value. It only addresses date and an erroneous gender, ignoring latitude, longitude, and timezoneOffset. The output (Kua number and group) is mentioned but not detailed sufficiently.

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 description mentions a 'gender' parameter, but the input schema does not include a gender property. This is a critical error that misleads the agent. Although schema coverage is 100%, the description introduces an undocumented parameter, severely harming parameter clarity.

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 that the tool computes a personal Kua number from solar-year digit sum and gender, and maps it to East/West group for direction work. This is specific and distinguishes it from related tools like chinese_feng_shui_bagua and chinese_feng_shui_lucky_directions.

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 a group label ('Chinese — Zodiac & Feng Shui') and an example request body, implying its use for Feng Shui direction work. However, it does not explicitly state when to use this tool versus alternatives or provide exclusions. Usage is implied but not clearly delineated.

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