14 Main Stars

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

Annotations already declare the tool as read-only, non-destructive, and idempotent. The description adds minimal behavioral context ('theme/archetype') but fails to describe the output format, pagination, or other traits. With no output schema, the description should carry more burden.

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 concise (one sentence plus group tag and example). The example request body is helpful. However, the grouping information could be better integrated, and the structure is minimal.

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 of Zi Wei Dou Shu and the absence of an output schema, the description should detail the return structure (e.g., list of stars with names and themes). It only mentions 'theme/archetype' but is incomplete for agent understanding.

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%; all four parameters are documented in the schema. The description reinforces the required 'date' via example but adds no extra semantics beyond what the schema provides for latitude, longitude, or timezoneOffset.

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 '14 canonical Zi Wei main stars with theme/archetype', specifying the exact resource and scope. The title '14 Main Stars' further reinforces this, distinguishing it from sibling tools like ziwei_full_chart or ziwei_palace_*.

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 includes a group tag 'Zi Wei Dou Shu (Purple Star) — MVP' but provides no explicit guidance on when to use this tool versus alternatives. The example request body implies a use case, but lacks exclusions or comparisons to sibling tools.

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