bazi_annual_pillar

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safe read nature is covered. The description adds credit cost and explains the NaYin concept, which goes beyond structured data. No contradictions found.

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-organized with a clear first-sentence purpose, a domain explanation, bullets for use cases, and an example. The NaYin explanation is helpful but slightly verbose; overall it earns its place.

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?

For a single-parameter lookup tool with rich annotations, the description lists all return fields, provides an example, and includes credit cost. It is complete enough for invocation, even without an output schema.

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 covers 100% of the single parameter 'year' with range and example. Description adds an example call (year=2025) but does not provide additional semantic nuance beyond the schema.

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?

Description explicitly states 'Look up the sexagenary pillar for any Gregorian year' and lists the returned attributes. This is a specific verb+resource+scope and distinguishes from sibling tools like explore_bazi_chart by focusing solely on the annual pillar.

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 a 'Use this to' bullet list with clear use cases (e.g., identify energetic quality, determine birth year pillar, find NaYin). However, it does not explicitly mention alternatives or when not to use it, only implying context.

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