xiaoliuren_cast

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

With no annotations, the description must carry the behavioral burden. It does state a critical integrity rule, 'The host MUST NOT invent the cast', and flags the optional lunar-python dependency. It does not disclose side effects, permissions, error conditions, or whether the result is deterministic, so behavioral disclosure is only partial.

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 tight sentences deliver the purpose, the no-invention constraint, and the mode-dependent input requirements with no filler. Important information is front-loaded and every clause 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 output schema covers return values, and the description covers method-to-parameter mapping and the dependency caveat. Still, the ambiguity between method=time and method=lunar_time, plus the unstated lunar meaning of month/day/hour, leaves real gaps for an agent trying to select the correct invocation.

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 description coverage is only 40%, and the description compensates by mapping methods to required parameters: numbers needs month/day/hour, while time modes need datetime. This adds conditional meaning beyond the schema, though it leaves the lunar-calendar basis of the numeric inputs implicit.

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 opening phrase 'Cast Xiao Liu Ren (小六壬)' uses a specific verb and resource, and the subject clearly separates it from sibling tools such as bazi_cast, tarot_draw, and iching_cast. The rest of the description clarifies the casting modes rather than blurring the purpose.

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 gives concrete conditions for method=numbers versus method=time/lunar_time, so an agent knows which parameter group is needed. However, it does not explain the difference between method=time and method=lunar_time beyond the dependency, and it never tells an agent when to choose this tool over the sibling divination tools.

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