八字/六爻 AI 深度解读

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

With no annotations provided, the description carries the full burden and does so admirably. It discloses the cost and billing method, the need for server-side credentials (LINGJI_TOKEN or LINGJI_PHONE+LINGJI_PASSWORD), and clarifies that this tool, unlike paipan interfaces, is the analysis layer. This gives the agent insight into side effects and dependencies.

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 compact yet information-dense, with every sentence serving a purpose: cost, differentiation, usage trigger, data source, workflow, and prerequisites. It is front-loaded with the core function and pricing, making it easy to scan.

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 tool's moderate complexity (5 params, no output schema, 9 siblings), the description is remarkably complete. It covers what the tool does, when to use it, how to obtain/load inputs, the cost, and required setup, leaving no critical operational gaps for an agent.

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 schema already covers all parameters with descriptions (100% coverage), but the description adds valuable cross-tool semantics by explaining that bazi and gua_data correspond to return objects from bazi_paipan/liuyao_paipan and by noting the default role and prompt_type behavior. This goes beyond the schema's bare field descriptions.

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 identifies the tool as a paid ('3元/次') professional fortune-telling interpretation service, with a specific verb ('深度解读') and resource (八字/六爻 interpretation). It also explicitly distinguishes itself from sibling paipan tools by stating they '只输出结构化数据、不做分析,' making the tool's unique purpose unmistakable.

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?

Provides explicit when-to-use guidance: whenever a user asks for interpretation, analysis, judgment, or advice, this tool must be called rather than the paipan interfaces, and the agent should not guess. It also gives a clear workflow: pass bazi_paipan/liuyao_paipan output directly, or load a saved chart with record_load first, plus a prerequisite about server account configuration.

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