cn402_fengshui_24shan

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

With no annotations, the description carries full burden but only hints at returned data (trigram parent, element, yin/yang). It omits output format, side effects, rate limits, or that it is a read-only lookup. The irrelevant price line adds confusion.

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 verbose, listing multiple synonyms in the first sentence, and includes an irrelevant pricing line. It could be condensed to one sentence stating the lookup action and returned data.

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?

Given the absence of an output schema and numerous siblings, the description fails to specify the operation type or provide examples. The agent cannot deduce whether the tool returns a single result or a list, or how to use the optional parameters effectively.

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% with clear descriptions for degree and name. The description adds minimal extra context (e.g., each span 15°) but does not clarify relationship between parameters or when to use each. Baseline 3 is appropriate.

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 defines what the 24-Mountain compass is but does not state the action (e.g., lookup, retrieve). It reads like a textbook entry rather than a tool purpose, making it vague for an AI agent to understand what the tool actually does.

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 sibling fengshui tools like cn402_fengshui_direction or cn402_fengshui_bagua-direction. The agent is left to guess the appropriate context.

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