get_natal_chart

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

No annotations provided. Description only states 'calculate', implying read-only, but lacks details on auth, rate limits, or side effects. Mentions timezone improves accuracy, but overall minimal behavioral disclosure.

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: one for purpose, then a bulleted Args list with inline examples. No redundant information. Front-loaded with key action and output components.

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?

Output schema exists, so description does not need to detail return values. Input parameters are fully covered with examples and notes. Could briefly mention that chart includes all listed components, but otherwise complete.

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?

Input schema has 0% description coverage. Description adds meaning with examples (e.g., '1994-01-26' for birth_date, '07:11' for birth_time) and clarifies format for timezone.

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?

Clearly states 'Calculate a complete BaZi natal chart with Four Pillars, Luck Pillars, Life Gua, and stars.' Differentiates from siblings like get_daily_pillars or get_luck_pillars which are subcomponents.

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 parameter descriptions with examples but no explicit when-to-use or when-not-to-use guidance. Context signals indicate siblings are sub-tools, but description does not compare.

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