Destiny Palace (Ming)

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context not in annotations: the POST endpoint and the 5-credit cost per call, which matters for budgeting in an agent loop. It does not disclose what the response contains or how birth time affects the result.

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 gloss line is front-loaded and wastes no words, and the bracketed metadata block is scannable. However, the metadata lines crowd out the substantive explanation, so it is terse without being informative.

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?

An output schema exists, so return values need not be explained, but for a birth-data-driven astrology computation the definition never indicates that time and timezone meaningfully change the palace result. Missing that leaves an agent unable to judge input quality requirements.

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 only 50%: timezone and timezoneOffset have rich schema descriptions, but date and time have none. The description only restates '[Required: date]', which duplicates the schema's required array, and says nothing about why a birth time is needed for Zi Wei palace placement.

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?

States a specific interpretable resource: the Destiny (Ming) palace of a Zi Wei Dou Shu chart, glossed as 'life path, character, soul mission'. That is more concrete than a bare name, but it does not distinguish it from siblings like astroway_ziwei_twelve_palaces or astroway_ziwei_full_chart, which also surface the Ming 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?

No guidance on when to call this versus the twelve_palaces/full_chart companions, nor any prerequisite such as needing birth time for a correct palace placement. Only the transport metadata (endpoint, required field, cost) is given.

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