get_van_han

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

No annotations provided. The description implies a read-only calculation but does not explicitly state side effects, idempotency, or behavior when defaults are applied. The parameter list adds some context but lacks detail on response format or errors.

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 well-structured with a clear purpose sentence followed by a bulleted parameter list. It is appropriately sized for the number of parameters, though slightly verbose.

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 complexity (9 params, no output schema, no annotations), the description covers purpose and parameter details adequately. It lacks information about return format or examples, but is sufficient for basic usage.

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 includes an Args block that provides semantic meaning beyond the schema, such as hour_val examples ('14:30', 'Ngọ') and is_solar explanation. Although schema description coverage is 0%, the description compensates well.

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 tool calculates transit stars and active houses for luck inspection, using specific terminology (Đại Hạn, Tiểu Hạn). It distinguishes itself from sibling tools like generate_horoscope which likely creates full horoscopes.

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 explains when to use it (current month/year inspection) and lists parameters with defaults. However, it does not explicitly state when not to use it or contrast with alternatives like get_saved_horoscope.

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