Children Palace (Zinu)

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile is covered. The description adds genuinely new operational context: the POST endpoint and a cost of 5 credits (Tier ½), which is useful for budgeting calls. It still says nothing about what the palace result contains or how it relates to an input chart, so it is adequate rather than rich.

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?

Very short and front-loaded: the topical keywords come first, then compact bracketed metadata tags for group, endpoint, required input and cost. Little waste, though the keyword line is so terse that it buys brevity at the cost of clarity.

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 no explanation, and the endpoint/cost tags cover operational needs. However, for a natal-chart-derived tool the description never states that date (and optionally time/timezone) are the subject's birth data, nor how it relates to the sibling Zi Wei chart tools — a meaningful gap for correct invocation.

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?

At 50% schema coverage, the description should compensate, but it only repeats that 'date' is required — already enforced by the schema's required list and pattern. The 'time' parameter has no description anywhere, and the description never clarifies that date/time are birth data or how time changes 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?

The description is a keyword blob ('Children, fertility, juniors.') rather than a verb+resource statement; the actual operation (deriving the Children palace of a Zi Wei Dou Shu chart) is only inferable from the title and the '[Group: Zi Wei Dou Shu]' tag. It is distinguishable from siblings like astroway_ziwei_palace_spouse only via the single word 'Children'. Vague purpose overall.

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 indication of when to choose this palace tool over astroway_ziwei_chart, astroway_ziwei_full_chart, or astroway_ziwei_twelve_palaces. '[Required: date]' is a schema fact, not usage guidance, and there are no stated prerequisites or exclusions.

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