cn402_fengshui_bed-direction

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

With no annotations provided, the description carries the full burden. It states the computation method and mentions an auto-paid price, but does not disclose the output format, potential errors, or any side effects. The behavioral information is adequate for a simple deterministic tool but lacks explicit details about cost implications or return structure.

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 includes multiple synonyms and a price note, which adds redundancy and extraneous information. The core functional sentence is clear, but the structure could be streamlined to remove the price line and repetitive translations without losing clarity.

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?

For a simple two-parameter tool, the description explains the method and purpose well. However, it does not describe the output (e.g., returns a direction like 'East'), which leaves the agent guessing. With no output schema, this is a notable omission. The completeness is adequate but not thorough.

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 input schema has 100% coverage but only provides minimal descriptions ('M | F', 'Birth year YYYY'). The description adds significant context by explaining that these parameters are used to compute the kua number via the Ba Zhai method, thereby linking parameters to the underlying logic. This goes beyond schema basics.

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 explicitly states the tool's function: to calculate the optimal bed direction based on kua number using Ba Zhai method. It provides multiple synonyms and clarifies the specific kind of direction (head direction). This clearly distinguishes it from sibling tools that focus on other fengshui aspects like business direction or general direction.

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 does not specify when to use this tool over alternatives. It omits prerequisites (like needing the user's kua number) and does not mention scenarios where it would be inappropriate. No guidance is given on choosing this tool among the many fengshui tools in the sibling list.

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