Children Palace (Zinu)

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds no additional behavioral context (e.g., what the tool returns, side effects, or prerequisites). It does not contradict annotations.

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 very concise but at the expense of clarity. It front-loads keywords effectively but lacks a clear statement of the tool's function. The example is helpful but 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 existence of many palace siblings, the description is insufficient. It does not explain the output (no output schema), prerequisites, or how the tool fits into the broader system.

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 coverage is 100%, so all parameters are documented in the input schema. The description provides an example request body, adding marginal value. However, it does not explain how the date relates to children/fertility interpretation.

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 states 'Children, fertility, juniors' which indicates the domain but does not specify the action (e.g., 'calculate', 'interpret', 'get'). The example request body hints at usage, but the purpose is vague for an agent selecting among many palace tools.

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 use this tool versus sibling palace tools like ziwei_palace_career or ziwei_palace_wealth. The group label 'Zi Wei Dou Shu (Purple Star) — MVP' provides context but no differentiation from similar tools.

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