Bagua Life Areas

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

Annotations already declare readOnlyHint=true, idempotentHint=true, etc. The description adds only that it uses Eastern-school Bagua and maps life areas, but does not explain how the input date or other parameters affect the mapping, nor the output format.

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?

Two sentences plus a group label and example. The core description is clear but the example is misplaced and confusing. Could be more structured and front-loaded with actionable information.

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 tool has 4 parameters (1 required) and no output schema. The description does not explain the output, how to interpret the mapping, or what the compass sectors mean. It is incomplete for an effective tool invocation.

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%, but the description adds no value beyond the schema. Worse, the example includes 'gender' which is not a parameter, misleading the agent about required inputs. No explanation of how date, latitude, longitude, or timezoneOffset are used.

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 maps 9 life areas onto compass sectors, using Eastern-school Bagua. The verb 'mapping' and resource 'life areas' are specific. It distinguishes from sibling tools like chinese_feng_shui_kua (Kua number) and chinese_feng_shui_lucky_directions (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?

No guidance on when to use this tool versus alternatives. The example includes gender, which is not a parameter in the schema, providing confusing and potentially misleading usage context.

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