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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's one genuine addition is the operational cost tag ('5 credits, Tier ½'), which is useful context, but it says nothing about what the computation requires or how the palace reading is derived.

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 lines with no filler, and the domain keywords are front-loaded before the metadata tags. However, the brevity comes from omission rather than tight editing; there is almost no substance to be concise about.

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 the description still leaves the core operation, the required birth date/time context, and the relationship to sibling palace tools unstated. For a chart-computation tool with 6 parameters, this is under-specified.

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 only 67%, with `date` and `time` carrying no description in either the schema or the tool description. The description supplies no parameter meaning at all — no indication that date/time are the birth moment the palace is cast from — so it fails to compensate for the coverage gap.

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 gives the thematic domain of the Tianzhai palace (real estate, family home, ancestry) but never states what the tool actually does — no verb like 'compute' or 'return', and no mention that it produces the Property Palace of a Zi Wei Dou Shu chart. It also does nothing to distinguish itself from the many sibling palace tools (career, wealth, spouse, health), so an agent must infer the operation from the name alone.

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?

There is no guidance on when to call this versus astroway_ziwei_chart, astroway_ziwei_full_chart, or the other palace_* siblings. The only routing help is the group/cost metadata tags, which say nothing about selection conditions or prerequisites.

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