Get today's GENERAL energy (no person needed) — the 干支 (stem + branch) and the dominant 5-element character of the day. Useful when the user asks 'what kind of day is it', 'what's the energy today', or when an AI agent wants to add cosmic context to a generic suggestion without needing the user's birthdate.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | Optional ISO YYYY-MM-DD. Defaults to today (UTC). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It only describes the output but does not disclose behavioral traits like read-only nature, side effects, permissions, or data freshness. For a safety-critical evaluation, this is insufficient.
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, front-loaded with the core purpose and usage context. No redundant words; every sentence adds value.
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 covers the main purpose and use cases but omits output format details (no output schema), data source (traditional Chinese calendar), and limitations. Adequate for a simple tool but with noticeable gaps.
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 focuses on 'today' but the optional 'date' parameter can specify any date, creating potential confusion. It adds no extra meaning beyond the schema's parameter description, which already covers the format and default.
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 the verb 'Get', the resource 'today's GENERAL energy', and the specific output (stem+branch and dominant 5-element). It distinguishes from sibling tools by noting no person needed, making it unique among the listed tools like asktian_best_time_for_action or asktian_compatibility.
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?
It provides explicit use cases such as 'what kind of day is it' and when to add cosmic context without needing birthdate. It implicitly excludes personalized readings, but lacks an explicit 'when not to use' statement.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool covers a distinct aspect of Chinese metaphysics: timing actions, compatibility, personal daily readings, market predictions, name analysis, and general daily energy. There is minimal overlap, and descriptions clearly differentiate them.
All tools follow a consistent 'asktian_' prefix and use descriptive snake_case names. The pattern is uniform across all six tools, making it easy to infer their purposes.
With 6 tools covering the core offerings of a Chinese metaphysics service (timing, compatibility, daily readings, name analysis, general energy, and market signals), the count feels well-scoped and appropriate for the domain.
The tool surface covers major user intents for this domain: personal guidance, relationships, timing, name profiling, general energy, and a novelty prediction feature. No obvious gaps for the stated purpose.
