asktian_today_energy

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

No annotations, but description fully discloses what the tool returns (stem+branch, dominant 5-element). It does not mention side effects or auth needs, but for a read-only computation tool this is acceptable. The description is transparent about behavior.

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, no wasted words, front-loaded with purpose. 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 is complete for a simple tool with one optional parameter and no output schema. It covers purpose, usage, and output clearly. No missing information needed for an AI agent to use it correctly.

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% for the single parameter, and the description adds context ('Optional ISO YYYY-MM-DD. Defaults to today (UTC)'). The description does not further enhance parameter semantics beyond what the schema provides, so 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 clearly states 'Get today's GENERAL energy' and specifies the outputs (干支 + dominant 5-element). It distinguishes from siblings by emphasizing 'no person needed' and that it's for generic context without birthdate.

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?

Explicitly describes when to use: when user asks about 'what kind of day' or for generic cosmic context without user's birthdate. Implies when not to use (when personalized info is available), with sibling tools provided for alternatives.

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