Lucky / Unlucky Directions

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

The description includes an example request body with a 'gender' field that is not present in the input schema, creating a misleading expectation about required parameters. This contradicts the actual behavior specified by the schema.

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 very short with two sentences and an example, but the example introduces a harmful inaccuracy. Otherwise, it is concise and 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?

The description lacks explanation of how the Kua number is derived, does not mention that gender is required but omitted from the schema, and provides no details about the output format. The example inconsistency makes the description incomplete and misleading.

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 does not clarify the parameters beyond the schema, and the example includes an invalid parameter (gender). Since schema coverage is 100%, the description adds no meaningful value and instead misleads.

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 it returns personal 4 lucky and 4 unlucky compass directions from Kua using standard Pa Kua mapping. The tool name and title align, and it distinguishes from related sibling tools like chinese_feng_shui_bagua and chinese_feng_shui_kua.

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 no explicit guidance on when to use this tool versus alternatives. It includes a group tag but no context on use cases, prerequisites, or when to avoid it.

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